Re: svn commit: r13308 - branches/locking/subversion/libsvn_fs_base

Ben Collins-Sussman <sussman@collab.net> writes:

> On Mar 8, 2005, at 2:48 PM, Philip Martin wrote:
>>
>> Scenario 1
>> working copy A: create directory 'foo'
>> lock 'foo/bar'
>> working copy B: create directory 'foo'
>> commit 'foo' => fails because 'foo/bar' is locked
>>
>> Scenario 2
>> working copy A: create directory 'foo'
>> lock 'foo/bar'
>> working copy B: create file 'foo'
>> commit 'foo' => succeeds
>>
>> I don't think it's sensible for one of those commits to succeed and
>> one to fail.
>>
>
> At the moment, the client has zero support for locking nonexistent
> paths; it doesn't even allow locking of URLs yet.

I only follow the locking stuff sporadically, so whenever I try to
reason about lock behaviour I run into problems with what is
possible/allowed :)

In the mail here:

http://svn.haxx.se/dev/archive-2005-02/0070.shtml

I was told that locks apply to pathnames and that locking schedule add
files should be possible, so just add "create file 'foo/bar'" before
the "lock 'foo/bar'" step.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org