C. Michael Pilato wrote:
> Robin Sommer <sommer@in.tum.de> writes:
>
>
>>On Sun, Oct 17, 2004 at 15:00 -0500, kfogel@collab.net wrote:
>>
>>
>>>You don't want hooks modifying what's being committed.
>>
>>Yes, I saw the warning in pre-commit.tmpl. But I thought perhaps the
>>new property could be become a transaction of its own, just as if
>>some other person would have added it independently. I didn't see a
>>way to achieve this, though.
>
>
> You don't want to do this in pre-commit, because your propset will
> then cause your original commit to be out of date. Instead, you would
> do this in post-commit, probably using a 20-line bindings script. The
> real trick, though, would be making sure that your post-commit hook
> doesn't fire off for commits generated by itself -- that's a nice way
> to potentially wind up in an endless loop.
I hacked something like this in a post-commit hook, but I didn't like
how it effectively made many commits increase the revision number twice,
and how it makes your wc out of date right after committing.
Is there any plan to make it possible to set server-side policies, such
as auto-enabling svn:keywords on certain files for everyone, or whatnot?
- Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 19 10:03:48 2004