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

RE: Activities and Checkin/Merge

From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 15 Jan 2002 08:46:21 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B1056E19E0@SUS-MA1IT01>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
If the working resources were created by checking out VCR's
with DAV:apply-to-versoin, then there is no difference between
checking in the activity and MERGEing the activity with
DAV:checkin-activity set.

The only reason DAV:checkin-activity is provided as a parameter
to MERGE is to support clients that create working resources by
checking out versions (in which case checking in the activity just
creates new versions, while MERGE both creates the versions and
merges them to the specified collection.


-----Original Message-----
From: Kirmse, Daniel [mailto:daniel.kirmse@sap.com]
Sent: Tuesday, January 15, 2002 6:43 AM
To: Ietf-Dav-Versioning (E-mail)
Subject: Activities and Checkin/Merge


suppose I have a repository landscape with a workspace under
baseline-control. The workspace contains my VCR's. Checkout is done with
DAV:apply-to-version and DAV:activity-set (href or new). So Work in process
is represented by working-resources collected in activities.

What is the difference of performing a checkin on the activity or do a merge
of that activity to the workspace the VCR's are located in with

Received on Tuesday, 15 January 2002 08:47:26 UTC

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