David Weintraub wrote:
> I don't even want the option to run hooks on client machines. It
> simply causes more problems than it is worth. I like the way
> Subversion handles hooks and I don't want it to change.
>
Agreed doing this from a commit hook would not be practical. I was just
looking for a hack.
The real solution is to put the config file for a project into the
project, that would do the trick. Seems like a pretty simple
modification to svn.
When the svn command is run, it would load the config file from the
usual locations, and then it would load one from the project if it
exists. Having the config file complete separate from the projects is a
real pain. Without fail anyone that converts from CVS to SVN at my
company complains about this issue. They try to do a commit and the
commit hook yells at them, then they spend 15 minutes or so trying to
figure out how to put the config file in the right place for the
particular installation of svn. Then they have to restart and try to
add the files all over again. Or run the set mime stuff from the
command line.
-Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-25 16:35:01 CEST