John Peacock <jpeacock@rowman.com> writes:
> Mark Grosberg wrote:
> > Right now we try to do the keywords on each commit and put them in
> > by hand; but an automated system where we can simply put the rules
> > in a Perl script would be nice. This is an actual use case for the
> > way we use subversion at work.
>
> Nothings stopping you from doing this now, even without server
> hooks. Just define $SVN_EDITOR to be a Perl script on the client which
> does whatever magic mangling you want. Just because the project
> doesn't want to support client hooks (for any number of reasons),
> doesn't mean you cannot write your own.
That's a very good point (that client-side scripting is effectively
supported for log messages, via $EDITOR).
However, it would be very hard to ensure that every client runs the
same script. Since log-message templates are a matter of *repository*
policy, not working copy policy, it is appropriate for the server to
be the place where the logic happens.
I'm not sure if that point has been made explicitly in this thread
before now; sorry if it's a repeat.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 20 18:38:31 2005