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

Re: Enforcing the lock of a file prior to its commit.

From: Johan Appelgren <johan.appelgren_at_gmail.com>
Date: 2006-07-21 11:07:09 CEST

On 7/21/06, Luca Cappa <luca.cappa@sequoia.it> wrote:
> On Thu, 20 Jul 2006 15:31:57 +0200, Johan Appelgren
> <johan.appelgren@gmail.com> wrote:
> >
> > Have you looked at writing a pre-commit hook that does what you want?
> >
> > That wouldn't stop anyone from editing a file, then get the lock and
> > then commit though. So I'm not sure what you'd gain?
> I would gain that the person needs to get the lock. If the lock is already
> being held
> by someone else, this guy is warned that the next time he removes the
> read-only flag
> (and changes it and then fails to lock it) he will remember to check if
> there is
> already any lock on that file prior to apply any modification to it.

But this will educate them after they spent countless hours modifying
a unmergable file that they then can't commit. I'd think it would be
better to teach them what the read-only flag for files mean before
they make that mistake?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 21 11:08:29 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.