Well, his original objection was about spending 4 hours working on
something only to find out it
was a waste of time upon commit when SVN complains about merging the
changes because
"the other guy" commited first.
The only thing a pre-commit trigger does is change the message, not the
fact he will still waste 4 hours
working on something he doesn't know 'joe' is also changing in HIS
personal working copy.
This calls for a trigger on checkout to look at a property and mark the
files read-only in your local working
copy based on a property as in your example #2.
Any undocumented functionality along these lines?
Toby Johnson wrote:
> pkahn@connected.com wrote:
>
>> If you have any other cleaver idea or if you know of any places I
>> could go look for solutions, I'd love to read about them...
>>
> Exclusive locking is the "next big feature" that the devs are planning
> on working on for 1.2.
>
> In the meantime, if this is a necessity for you I would implement this
> using a pre-commit hook script. Two approaches I would look into are:
>
> * have a text file where each line is a file URL followed by a tab and
> a username. The pre-commit hook looks at this file for attempts to
> commit a certain URL, and if the URL exists in the file then only the
> specified username is allowed to commit.
>
> * create your own versioned property, the value of which is a
> username. The script looks at the property instead of the text file.
>
> These are basically short-term hacks until a "real" system based on
> tokens is implemented.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 16 22:07:36 2004