Next message: Greg Stein: "Re: move/copy/delete/etc in a change set"
Message-Id: <200008101823.OAA24051@tux.w3.org>
Date: Thu, 10 Aug 2000 14:23:09 -0400
To: ietf-dav-versioning@w3.org
From: Eric Sedlar <eric.sedlar@oracle.com> (by way of "Ralph R. Swick" <swick@w3.org>)
Subject: Re: move/copy/delete/etc in a change set
[released from spam trap -rrs]
Date: Thu, 10 Aug 2000 13:41:07 -0400 (EDT)
Message-ID: <3992E947.6693715B@oracle.com>
From: Eric Sedlar <eric.sedlar@oracle.com>
Organization: Oracle Corporation
To: Greg Stein <gstein@lyra.org>
CC: ietf-dav-versioning@w3.org
All this is captured by versioning collections, isn't it?
Greg Stein wrote:
> I'd like to enable change sets (i.e. a transacted set of changes to a DeltaV
> repository) that includes MOVE, COPY, DELETE, MKCOL, or PUT. However, it
> appears that each of these are spec'd as taking place immediately against an
> auto-versioned collection.
>
> Is there a way to do this?
>
> If not, then I would suggest we add something. These kinds of changes can
> definitely occur in a change set.
>
> For example, consider a repository for code development. I can easily see
> torching an old interface (DELETE), adding a new one (PUT), create a subdir
> for some new tests for the interface (MKCOL), and moving a test from an old
> into the new, along with some changes to that file (MOVE and PUT).
>
> Thoughts?
>
> Thx,
> -g
>
> --
> Greg Stein, http://www.lyra.org/