[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-20 15:31:57 CEST

On 7/20/06, Luca Cappa <luca.cappa@sequoia.it> wrote:
> Hello Greg,
>
> In Thu, 20 Jul 2006 14:54:12 +0200, Greg Thomas <thomasgd@omc.bt.co.uk>
> wrote:
>
> > On Thu, 20 Jul 2006 09:37:18 +0200, "Luca Cappa"
> > <luca.cappa@sequoia.it> wrote:
> >
> >> i am searching for a way to prevent that a not locked file could be
> >> committed. I think
> >> i could achieve that writing on my own a prehook script, but i am
> >> searching for a
> >> working out of the box solution. Any help?
> >
> > I may be missing something, but would
> >
> > svn propset svn:needs-lock yes /path/to/file
> >
> > do the job?
> >
>
> No, cause if you try it, you could commit a file with that property set
> even though you havent locked it. The trick is to just remove the
> read-only flag on that file, modify it and then commit it. Try it and you
> will see
> that locks as they are appear to be totaly useless.
>
>
> Luca
>
> p.s. Please do not start arguing about the meaning of the life and so on,
> i need that feature as i said (i would like to commit only if the file was
> prior locked by the commiter).

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?

/Johan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 20 15:33:54 2006

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