[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 18:50:30 CET

On Thu, 16 Dec 2004, [UTF-8] Branko ─^Libej wrote:

> Peter N. Lundblad wrote:
> >On Wed, 15 Dec 2004, Julian Foad wrote:
> >
> >>>John Szakmeister wrote:
> >>>O.K., unlock the file, but only if it's an explicit target (I count any
> >>>file in a subtree of a directory target to be explicit fo this case).
> >>>
> >>>
> >What would be an non-explicit target? The implicit "."? That would be
> >inconsistent. Saying "svn ci foo.c" won't commit bar.cin the same
> >directory. Just trying to understand what you meant here, brane.
> >
> >
> Actually, I find that I don't know myself what I meant here... possibly
> that we don't unlock "bar/qux" if you commit "foo", but that's obvious.
OK. We are in aggreement then.

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:-)


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