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

RE: Version-controlled collection CHECKOUT

From: Kirmse, Daniel <daniel.kirmse@sap.com>
Date: Mon, 11 Feb 2002 14:31:57 +0100
Message-ID: <59357A260E15D311B5A60008C75D3530068B47C0@dbwdfx13.wdf.sap-ag.de>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
Some more detail:

I've checked out a collection. So I get a working collection. Now I put a
file to the working collection (adding a file to the repository). At checkin
a vcr for the newly added file is created (with all its dependend resources)
the checked in version of the collection is written to the
activity-version-set. What about the checked in version of the added file?
Is it written to the DAV:activity-version-set property too?


-----Original Message-----
From: Clemm, Geoff [mailto:gclemm@rational.com]
Sent: Mittwoch, 16. Januar 2002 15:59
To: Ietf-Dav-Versioning (E-mail)
Subject: RE: Version-controlled collection CHECKOUT



-----Original Message-----
From: Kirmse, Daniel [mailto:daniel.kirmse@sap.com]
Sent: Wednesday, January 16, 2002 8:36 AM
To: Ietf-Dav-Versioning (E-mail)
Subject: Version-controlled collection CHECKOUT


does the checkout behavior of a version-controlled collection be the same as
the checkout behavior of a version-controlled resource with
DAV:apply-to-version flag? (Because of working-collection sounds similar to
Is there the same behavior for parallel development (parallel checkouts,
checkin behavior) as for working-resources?

Received on Monday, 11 February 2002 08:38:13 UTC

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