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

Re: Locking: RFC: svn:needs-lock behaviors (Updated)

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-02-03 02:03:39 CET

On Feb 2, 2005, at 5:49 PM, Philip Martin wrote:

> Greg Hudson <ghudson@MIT.EDU> writes:
>> To the best of my knowledge, you should be able to lock schedule-add
>> files just fine. Locks apply to pathnames, not nodes or node-revs.
> The documentation in notes/ doesn't mention such locks, although it
> doesn't exclude them either, is there a plan to implement this sort of
> lock without node?

The repository already allows locks on nonexistent paths. (DAV clients
sometimes do this as a way of 'reserving' a path.)

I'm not entirely sure that svn_ra_lock() allows it -- we should double
check the three RA layers.

> There are all sorts of corner cases: if I have a
> schedule add directory 'foo' and I lock the path 'foo/bar' does that
> stop someone else commiting a new 'foo'?

 From the repository's point of view, yes. It should enforce the lock.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 3 02:06:09 2005

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.