On 15 March 2012 18:53, Bob Archer <Bob.Archer_at_amsi.com> wrote:
>> 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?
The OP wants to put a lock on the svn:external properties so that
developers can make local changes but cannot commit any changes to
this property.
Simon
--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2936270
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-03-15 21:06:54 CET