On Tue, Oct 19, 2010 at 10:04, Loritsch, Berin <bloritsch_at_dtri.net> wrote:
>> From: Andy Levy [mailto:andy.levy_at_gmail.com]
>> >
>> > I have gone through the link, but unable to find any
>> commands there...
>> > or the way to implement the locking mechanism.
>
> The key bit of information is adding the "svn:needs-lock" property to
> the files that require locking. In my experience, only Word documents
> really need this type of restriction because they are more prone to the
> type of workflow that supports.
>
>> You need to hook scripts on the server:
>>
>> Pre-lock - reject any lock without a message (just like
>> rejecting a commit in pre-commit with no log message).
>
> This would satisfy your #2 requirement.
>
>> Pre-commit - reject any added file without svn:needs-lock
>> set, or any commit which deletes svn:needs-lock from an existing file.
>
> This adds protections you didn't ask about. Personally, I would limit
> svn:needs-lock to only the files that really need it (like MS Office
> documents). For source code it actually gets in the way, and the
> copy-modify-merge model works much better.
I read this:
>1) Mandatory lock [No one should be able to modify the file unless they lock it ?]
as "we want to enforce locking on all files". I agree with you that
enforcing locking unilaterally is an "anti-best practice" in
Subversion.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2673492
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-10-19 17:02:19 CEST