Re: Is it possible to set svn:keywords using pre-commit hook script?

The best thing to do is provide an auto-properties "config" file for
your users to use -- complete with instructions on how and where to
install it.

Then create a pre-commit hook script that rejects any commits that
fail to set this property up properly. As part of the reject, give the
location of the read-me that has the information about
auto-properties. For example, if you have a company wide Wiki, put the
directions and a copy of the auto-properties file there.

It doesn't take more than two or three failed commits before even the
most stubborn developer falls into line and installs the right
autoproperties in their configuration.

I have a Perl script that checks for read/write/add permissions,
checks for invalid file names, and also verifies that properties are
set to their correct values. It's what I use to enforce this type of
situation.

--
David Weintraub
qazwart_at_gmail.com
On Tue, Nov 11, 2008 at 1:02 PM, vinay i <vinay.indresh_at_gmail.com> wrote:
> Hello All,
>
> I would like to set svn:keywords on all known non-binary files (if it is not
> already set) during a commit. Is this feasible? Because pre-commit hook
> script takes two arguments as inputs ( repository and transaction) and
> doesn't have information regarding the files being committed. How to
> identify the list of files on which the svn:keywords property has to be set?
>
> Thanks
> Vinay
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org