W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2001

Why does MERGE automatically checkin resources related to activit ies?

From: Peter Raymond <Peter.Raymond@merant.com>
Date: Fri, 28 Sep 2001 18:38:31 +0100
Message-ID: <20CF1CE11441D411919C0008C7C5A13B02AD2EFD@stalmail.eu.merant.com>
To: ietf-dav-versioning@w3.org

I was reading section 13 with a group of other staff in MERANT and we came 
across section 13.12 which talks about automatically checking-in any 
checked-out resources referenced by an activity which is specified as part 
of the DAV:source set for the MERGE.

Why does MERGE behave like this for activities and not for other resources 
(see the precondition DAV:cannot-merge-checked-out-resource in section 11.2.

This auto-checkin behaviour seems to add more complexity to the
of MERGE and seems to be inconsistent.  What was the use case for including
auto-checkin behaviour only for activities?

Peter Raymond - MERANT
Principal Architect (PVCS)
Tel: +44 (0)1727 813362
Fax: +44 (0)1727 869804
WWW: http://www.merant.com
Received on Friday, 28 September 2001 13:40:06 UTC

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