W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2002

RE: MERGE of Activity

From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 12 Feb 2002 08:26:55 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B105CE0B6B@SUS-MA1IT01>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
   From: Kirmse, Daniel [mailto:daniel.kirmse@sap.com]

   suppose this (strange) case:

   1. A file F was added to the repository.  With checking out the
   version-controlled collection C with an activity A1 with
   apply-to-version, putting the file to the working collection,
   checking in the activity (new version CV2 of the collection and
   first version FV1 of the added file going to activity-version-set

   2. Change a property of the collection C 
   With checking out C with activity A2 with apply-to-version, proppatch and
   checkin of A2. Version CV3 goes to the activity-version-set.

   3. Now MERGE activity A2 to a collection C' in a different workspace. C'
   does not contain the file F yet, because activity A1 was not merged to
   What happens here? Well the merge of CV3 into C' would succeed. But what
   about the binding to F? Will there be a new VCR for F pointing to the
   version-history of F with checked in version of that vcr is undefined?


Note that some CM systems will say "CV3 depends on CV2, and CV2
is produced by A1, so you can't MERGE A2 unless you also MERGE A1",
but that is not required by DeltaV.

Received on Tuesday, 12 February 2002 08:27:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:48 UTC