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

Re: Locking non-existent paths. Time to discuss.

From: Brian W. Fitzpatrick <fitz_at_collab.net>
Date: 2005-03-17 03:52:14 CET

On Mar 16, 2005, at 4:37 PM, Ben Collins-Sussman wrote:

> 2. punt on locknull support in the client.
> - 'svn st -u' will not show lock-nulls.
> - 'svn info URL' will not show lock-nulls.
> - 'svn ls' will not list lock-null children.
> - 'svn lock/unlock URL' won't work on nonexistent paths.
> - 'svn lock wcpath' won't work on schedule-add paths.
> In theory, we've been worried about the scenario where a DAV
> client creates a lock-null resource, and then this starts to effect
> svn clients adversely. (e.g. an svn client tries to delete a
> directory, gets a locking error, but can't see the lock!) But our
> epiphany today was that in *practice*, lock-null resources don't last
> for more than a microsecond. The probability of affecting an svn
> client is miniscule. So we'd rather punt on these client features,
> and simply leave the door open to add them in svn 1.3 if there's
> demand.

I'm +1 all over that.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 17 03:53:25 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.