On Jul 30, 2009, at 07:02, axdmoraes wrote:
> Ryan Schmidt wrote:
>
>> I would suggest you do both of these things:
>>
>> 1. Set up auto-props on every client computer so that every file
>> automatically gets the svn:needs-lock property added.
>>
>> 2. Write a pre-commit hook in the repository so that any commit of a
>> new file that does not have the svn:needs-lock property gets
>> rejected.
>>
>> In this way, you ensure that all files in the repository will have
>> the svn:needs-lock property on them, which will require everyone to
>> "svn lock" a file before they can edit it.
>>
>> Note that by default any user can steal any other user's lock. I
>> believe there are more hook scripts you can write to prevent that.
>
> Now I see how to deal with it. It´s harder than I thought, because
> configure
> every client is painful.
> But it´s the only way.
It's not that hard. Install a pre-commit hook preventing commits that
do not conform to your property policy. The error message your hook
scripts prints can tell the user how to set up their client, or even
tell them where to go to download a pre-made config file that they
can use on their system.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2377546
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-31 22:18:37 CEST