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

[Locking] commit and unlock

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2004-12-14 19:11:29 CET


The current locking spec says that svn commit unlocks locked files that
are committed by default. I think this is a good default to prevent people
from forgetting to unlock, but it seems there was no consensus, so it
might be time for some discussion.

If we have this default, there will be a --keep-lock(s|ed)? option to let
people keep their locks. As I said, this is good. Having people often
forget to unlock could develop a habit of stealing locks as a "normal" way
of working. Somebody might argue that this is mxing up commands.

IN any case there is the question if only the committables (the files that
were actually changed) or all files specified by the targets (and possibly
recursively) should be unlocked. I think the latter is the best. If you
commit a subtree with some locked files, a lock shouldn't be left just
becvause the file wasn't modified. This could also need some dicsussion, I

Any opinions?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 14 19:11:31 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.