Re: Pre-commit and post-chekout hooks on client side

> #1 use the hooks to 'Verify' the correct copyright info is included and
> reject the entire commit
> unless they are there and make the coders fix the problem.
> Give them a good template and make them do the job right.

... or, better still, provide them with a utility that fixes the
copyrights, that shows them the changes (with 'diff') before making them.
When they get a message "commit rejected because of copyright issues",
they simply run the script, check its changes for sanity, and try again
(possibly with a recompile of the affected files in between, to be on the
safe side).

This is what we use, and it works very well.

Patrick

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 8 00:14:54 2004