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

Re: [Locking] commits and unlock (revisited)

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-02-24 11:24:58 CET

On Tue, 22 Feb 2005, C. Michael Pilato wrote:

> "Brian W. Fitzpatrick" <fitz@collab.net> writes:
>
> > a) Upon commit, unlock all locked files in TARGETS
> >
> > PROS: - Helps when you forget to unlock files when you're done with
> > them.
> >
> > CONS: - If you want to make multiple commits to a file without
> > releasing a lock, you need to pass --no-unlock when
> > committing.
> >
> > b) Upon commit, unlock SOME locked files in TARGETS
> >
> > PROS: - Makes it easier to divide separate commits into changesets.
> >
> > CONS: - YASSC (Yet Another Subversion Special Case).
> > - Violates KISS.
> >
> > c) Upon commit, unlock nothing
> >
> > PROS: - Avoids possible conflicts in unmergeable files that are left
> > unlocked (although svn:needs-lock alleviates this somewhat).
> > - Doesn't overload commit with locking behaviors.
> >
> > CONS: - You can forget that they you have files locked and prevent
> > others from editing those files.
>
...
> So:
> (a) +1
> (b) -0.9999
> (c) +0
>
+1

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 24 11:24:13 2005

This is an archived mail posted to the Subversion Dev mailing list.