conflicts-report vs. merge-preview-report

From: Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Date: Thu, Jun 15 2000

Next message: Clemm, Geoff: "Versioning TeleConf Agenda, 6/19/00 (Monday) 2pm-3pm EST"

Previous message: Clemm, Geoff: "RE: Protocol doc"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Other mail archives: [this mailing list] [other W3C mailing lists]
Mail actions: [ respond to this message ] [ mail a new topic ]

Date: Thu, 15 Jun 2000 17:28:19 -0400 (EDT)
Message-Id: <200006152128.RAA17664@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: conflicts-report vs. merge-preview-report

I'd like to tighten the relationship between the MERGE method and
the conflicts REPORT.  In particular, currently, the conflicts report
only notifies you about merges, while the MERGE method tells you both
about merges and about changes to the default target selection.

So I'd like to add default-target selection changes to the output
of the conflicts report, and rename it the "merge-preview" report,
both to emphasize its relationship to merge, and to indicate that
it returns information on more than just conflicts.

Any objections?

Cheers,
Geoff

Next message: Clemm, Geoff: "Versioning TeleConf Agenda, 6/19/00 (Monday) 2pm-3pm EST"
Previous message: Clemm, Geoff: "RE: Protocol doc"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Other mail archives: [this mailing list] [other W3C mailing lists]
Mail actions: [ respond to this message ] [ mail a new topic ]