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

Re: svn commit: r11334 - in trunk/notes: . locking locking/old

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2004-10-13 19:39:58 CEST

--On Wednesday, October 13, 2004 1:12 PM +0100 Philip Martin
<philip@codematters.co.uk> wrote:

> Problems arise even without moves, consider editing, adding and then
> deciding not to add:
> $ svn lock dir/file1
> $ edit dir/file1
> $ svn lock dir
> $ svn add dir/file2
> $ svn revert dir/file2
> $ svn unlock dir
> - Can I lock dir when dir/file1 is locked, or will I have to
> revert/unlock my edit first?

I think if we implement directory locking and you hold a file lock already,
then you should be able to acquire the directory lock. If someone *else* has
an active lock on a file in that dir, then I guess 'svn lock' on a directory
should error out with a message from the server.

FWIW, I'm with C-Mike: I'd rather see directory locking not have any
inherited/recursive properties - it'd just lock any modifications, deletions
or additions to the directory.

> - Do I end up with two locks on dir/file1?

I wouldn't think so.

> - When I decide to revert/unlock the add, does that remove my lock(s)
> on dir/file1?

Good question. But, I'd think not. Nothing you did regarding file1 in your
example above was communicated to the server. -- justin

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