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

Re: [Locking] commit and unlock

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2004-12-16 19:09:19 CET

Ben Collins-Sussman wrote:
> On Dec 16, 2004, at 11:50 AM, Peter N. Lundblad wrote:
>> Do people agree that we unlock by default and don't on --keep-locked
>> switch? I'll assume so if I don't get massive objections:-)
> That certainly seems to be the consensus.

As usual, I'll recommend providing explicit switches for both ways, so that the
default need not be finalised in the first release that supports locking.
After one release worth of experience, we may have a better idea of what the
default should be, or whether the default should be configurable.

But I feel I'm rather alone in this view. Most people seem to want a default
to be decided and implemented straight away. If that's what we do, I'm happy
with the default being "unlock" (meaning unlock all of the targets) as
suggested above.

- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 16 19:10:52 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.