Philip Martin wrote:
>Branko ÄŒibej <brane@xbc.nu> writes:
>
>
>
>> * "svn commit" also accepts --lock, meaning "commit but keep the
>> lock". By default, "svn commit" releases all locks.
>>
>>
>
>Generally I like this, but.. does commit release directory locks?
>
> $ svn lock dir
> $ svn add dir/foo
> $ svn add dir/bar
> $ svn ci dir/foo
>
>Does the client have to detect the problem?
>
> $ svn ci dir/foo
> svn: commit would leave unlocked modifications
> svn: use --lock to preserve the locks
>
>Does it automatically add --lock as needed?
>
>Does it ignore the problem and leave the working copy with unlocked
>modifications?
>
>
It's a tricky question. ClearCase is different in that it doesn't have
the concept of an "uncommitted add", and you must always explicitly
check in the directory to make changes visible to others. Of course the
GUI will do all that for you.
I think the error-message approach would be best in this case; of course
the message must indicate which locks triggered it.
>Are directory locks too hard?
>
I don't think so.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 19 00:42:35 2004