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

Re: Locking functional spec: directory locks

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-10-13 17:42:15 CEST

Greg Hudson <ghudson@MIT.EDU> writes:

> The functional spec says:
> > If a directory is locked, the owner of the lock has the exclusive
> > right to change the directory's list of entries and properties, to
> > delete the directory, and to move the directory. This lock applies
> > recursively to all files and directories under the locked directory.
> I believe that if we want our locking implementation to be within the
> realm of acceptable simplicity, we need to punt on directory locks,
> which address a completely different need from the sane handling of
> non-mergeable files. For those who believe otherwise, please answer
> the following questions:
> * Does the svn:lock property on a directory imply that every file
> underneath the directory must be locked before modification, and
> should therefore be read-only in the working copy when not locked?

We needn't support the use of svn:lock on directories. In fact, I'd
we definitely shouldn't support that. Don't mix the ideas of
"supporting directory locking" with "supporting recursive
lock-acquisition requirements". For the record, I strongly support
the former, but really couldn't care much less about the latter.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 13 17:44:32 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.