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

RE: SVN lock on directory (property change only)

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Thu, 15 Mar 2012 14:53:00 -0400

> On 15 March 2012 15:25, Dale McCoy <dalestan_at_gmail.com> wrote:
> > On Thu, Mar 15, 2012 at 10:38,  <Dennis.Gertitschke_at_zf.com> wrote:
> >> We are using svn:externals property to set all our components to the
> >> currently released version (they reside in a separate components
> >> repository).
> >>
> >> The normal developer should not be allowed to commit changes to the
> >> svn:externals property (only locally in his working copy to continue
> >> development).
> >>
> >> So my idea was to always keep that property locked, but TortoiseSVN
> >> only allows me to lock files.
> >
> > A lock prevents the developer from changing whatever-is-locked, even
> > locally. For this workflow, I think you want a pre-commit script on
> > the server instead.
>
> Agreed.
>
> Locks are not binding, only advisory. And they are implemented by the
> subversion library, not TSVN, so there is no way to do what you are asking using
> current SVN functionality.
>
> Simon

My understanding is all a "lock" does nothing locally. If you have svn:needs-lock set all it does it set the local file to read only.

So, I do think you can lock the files and the users should be able to change them locally. What am I missing?

BOb

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2936241

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-03-15 19:53:09 CET

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

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