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

Re: [locking] out-of-dateness checking during lock

From: Michael Brouwer <michael_at_tlaloc.net>
Date: 2004-12-04 18:21:21 CET

Doesn't this mean that hitting ctrl-c at the right time might leave you
with
an out-of-date wc that is holding a lock?

Michael

On Dec 4, 2004, at 8:35 AM, Greg Hudson wrote:

> On Sat, 2004-12-04 at 11:14, Ben Collins-Sussman wrote:
>> * I'm worried that if an admin has post-lock and post-unlock hook
>> scripts, there's going to be 2 useless emails generated whenever
>> somebody even *attempts* to lock an out-of-date wc file.
>
> We can make this case much less common by checking for out-of-dateness,
> grabbing the lock, checking again, and releasing the lock if the second
> test fails.
>
>> I know that the idea of 'svn lock' automatically doing updates was
>> shot
>> down weeks ago, with people screaming about how bad it is to mix
>> subcommand concepts together. But now it seems the only alternative
>> is
>> to make the 'svn lock' command behave a bit schitzo: "lock the
>> file...
>> oh wait, nevermind, unlock it!" Is that behavior the lesser of two
>> evils?
>
> Yes, by a mile.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 4 18:22:51 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.