[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: Bruce DeVisser <bmdmail_at_look.ca>
Date: 2004-12-16 04:23:36 CET

On Wed, Dec 15, 2004 at 01:51:58PM +0100, Folker Schamel wrote:
> Bruce DeVisser wrote:
> > On Wed, Dec 15, 2004 at 02:53:36AM +0100, Folker Schamel wrote:
> >
> >>What is the practical advantage of not unlocking unmodified files?
> >
> >
> > Perhaps the locker wants to force the file to remain
> > unmodified (by anyone). Someone in an administrative
> > capacity might wish to do this as a partial code freeze.
> This argument holds in the same way for modified and
> unmodified files. -> so it is an argument for committing
> without releasing locks at all.
> -> but what is the practical advantage of unlocking
> modified, but not unlocking unmodified files belonging to
> the same commit?

Valid point, *if* you think committing modified files should
unlock them.

Personally I would prefer that it be a user-configurable
option, overrideable on the command line.


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