[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: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2004-12-16 21:46:16 CET

On Thu, 16 Dec 2004, 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.
How would you do without a default? Error out if a any lock is discovered?

If we want to add an option for the oposite later, or add it to the
configuration files, we might want to use --no-unlock (so we can add
--unlock). Opinions?


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