Next message: Geoffrey M. Clemm: "Re: move/copy/delete/etc in a change set"
Date: Thu, 10 Aug 2000 12:48:24 -0700
From: Greg Stein <gstein@lyra.org>
To: Eric Sedlar <eric.sedlar@oracle.com>
Cc: ietf-dav-versioning@w3.org
Message-ID: <20000810124824.D19525@lyra.org>
Subject: Re: move/copy/delete/etc in a change set
Yes. I had missed that. Geoff pointed it out in an earlier note. I still
have a couple minor questions (posted to the list in another email) that
I'll take a stab at if nobody has ideas off-hand.
thx,
-g
On Thu, Aug 10, 2000 at 10:41:27AM -0700, Eric Sedlar wrote:
> 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/
--
Greg Stein, http://www.lyra.org/