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

MERGE of Activity

From: Kirmse, Daniel <daniel.kirmse@sap.com>
Date: Tue, 12 Feb 2002 11:34:07 +0100
Message-ID: <59357A260E15D311B5A60008C75D3530068B47C9@dbwdfx13.wdf.sap-ag.de>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>

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 property)

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 C'.
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?

Received on Tuesday, 12 February 2002 05:34:52 UTC

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