[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Directory locking: current goals

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-10-15 21:06:20 CEST

Julian Reschke <julian.reschke@gmx.de> writes:

> Brian W. Fitzpatrick wrote:
>> - Depth 0 lock: lock only the directory properties. I don't know
>> how useful this might be.
>> - Depth 1 lock: lock the directory properties and the contents of
>> the directory. That is, no other user is able to add or delete
>> files from the directory, nor to modify any of the files in the
>> directory.

> I think it would be beneficial to keep terminology in sync with
> WebDAV. A shallow lock in WebDAV (depth = 0) locks the collection
> (properties and collection membership), so it would be a mix of the
> two levels you suggest.

I assume "collection membership" means adding and removing elements,
but not modifying existing elements. That's more or less the way
Clearcase works so it's likely to be feasible. The main difference is
that Clearcase requires the directory to be committed for adds/deletes
to take effect while Subversion allows the elements to be committed.

    $ svn lock dir
    $ svn rm dir/file1
    $ svn add dir/file2
    $ svn ci dir/file2

Clearcase doesn't allow that sort of commit, Subversion will need to
determine how it behaves: keep the lock, release the lock, reject the
commit client-side.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 15 21:21:53 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.