[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-17 22:05:28 CET

On Fri, 17 Dec 2004, Benjamin Pflugmann wrote:

> On Thu 2004-12-16 at 12:19:01 -0600, Ben Collins-Sussman wrote:
> [...]
> > That said, we could create a new ~/.subversion/config variable called
> > "commit-keeps-locks = yes", or "always-keep-locks" or something.
> Sorry, this is just kind of a drive-by proposal, but I didn't see it
> mentioned yet, so I thought I bring it up:
> How about something like
> svn lock [--persistent|--temporary]
> in addition to / instead of the user-config, which would note (only in
> the WC) with the lock whether to rather keep it or remove it on
> actions where a lock might reasonably be released (in practice, it's
> only "commit", isn't it?)
> The suggestion is because I see me using both kinds of
> "always-keep-locks" settings, depending on whether I expect to finish
> up fast (like in 1-2 hours) and do only one commit, or if I expect the
> work to consist of several stages (and so commits).
This could be one way of doing it, but I don't think it buys you anything
compared to the current spec. YOu could as well use --no-unlock on the
commit before running to the bus:-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 17 22:05:29 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.