[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: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-12-16 19:19:01 CET

On Dec 16, 2004, at 12:09 PM, Julian Foad wrote:

> 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.

I'm pretty sure this isn't an option. We try to resist adding extra
switches to command whenever we can, and it's a big no-no to *remove* a
1.2 switch in a 1.3 release.

So I think 'svn commit' will release locks by default, and have a
single --keep-locks option.

That said, we could create a new ~/.subversion/config variable called
"commit-keeps-locks = yes", or "always-keep-locks" or something.

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:21:57 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.