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

Re: Why does MERGE automatically checkin resources related to act ivities?

From: Greg Stein <gstein@lyra.org>
Date: Mon, 1 Oct 2001 04:21:14 -0700
To: "Clemm, Geoff" <gclemm@rational.com>
Cc: ietf-dav-versioning@w3.org
Message-ID: <20011001042114.Q24132@lyra.org>
On Fri, Sep 28, 2001 at 02:10:07PM -0400, Clemm, Geoff wrote:
> This was added to allow for an "atomic" activity checkin/merge request
> (something needed by the Subversion system), which only supports
> DAV:no-checkout merge requests.  With the new DAV:auto-update
> functionality, an alternative way of supporting this functionality
> would be to allow CHECKIN to be applied to an activity (and having it
> mean "checkin everything in that activity").  The DAV:auto-update
> functionality would do the MERGE.
> Greg: This just means you would replace your activity MERGE request
> with an activity CHECKIN request.  This would also significantly improve
> interoperability, since more systems are likely to support
> activity CHECKIN than are likely to support the MERGE feature.

I presume this would mean that I could check out a Baseline into the
activity, and that baseline would be checked back in with the activity? And
that the VCC would be updated?

But all that probably isn't going to help anyways. We check out version
resources. The DAV:auto-update mechanism does not work when dealing with
version resources.

> If there are no objections, I can make this change.  If there
> are *any* objections, I will not make the change, since we are
> so late in the draft process.

I object. :-)

The existing specification provides for an atomic check/merge of a set of
resources. Dropping the activities from the MERGE would eliminate that.


Greg Stein, http://www.lyra.org/
Received on Monday, 1 October 2001 07:17:42 UTC

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