- From: Kirmse, Daniel <daniel.kirmse@sap.com>
- Date: Wed, 13 Feb 2002 11:36:53 +0100
- To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
>To merge members of the collection version CV1 >into working collection WC2, you >would checkout CV1 (to get WC1), MOVE the members of >WC1 that you want into WC2, and then DELETE WC1. And this would apply independently of the fact wether the collection versions are versions of the same version-controlled collection or they are versions of two independent version-controlled collections? -----Original Message----- From: Clemm, Geoff [mailto:gclemm@rational.com] Sent: Dienstag, 12. Februar 2002 14:41 To: Ietf-Dav-Versioning (E-mail) Subject: RE: MERGE von Collections The DAV:version-controlled-binding-set is a readonly property on a collection version. To merge a collection version: To merge members of the collection version CV1 into working collection WC2, you would checkout CV1 (to get WC1), MOVE the members of WC1 that you want into WC2, and then DELETE WC1. To merge members of the collection version CV1 into checked-out version-controlled collection, VC2, you would need to select particular versions of the version histories identified by the DAV:version-controlled-binding-set of CV1, and then use VERSION-CONTROL requests to create version-controlled resources for those versions in VC2. Or if you are lucky, your server supports "auto-merge" for collections, and the server does this all for you. Cheers, Geoff -----Original Message----- From: Kirmse, Daniel [mailto:daniel.kirmse@sap.com] Sent: Tuesday, February 12, 2002 8:14 AM To: Ietf-Dav-Versioning (E-mail) Subject: MERGE von Collections Hi, simple question: How is a MERGE of collection versions done? Is it just a proppatch to DAV:version-controlled-binding-set? Regards, Daniel
Received on Wednesday, 13 February 2002 05:37:37 UTC