On Fri, Jul 20, 2001 at 05:10:37PM -0500, kfogel@collab.net wrote:
> We are closing in on self-hosting now, and it's time to write a hook
> system for the repository; would love comments & thoughts.
One thing I've often wanted is a hook to be able to modify the
incoming check-ins and outgoing check-outs. One use I have forseen
for this is coding standard formatting. The idea would be that upon
check-in a project-wide script would normalize the code to the
standard format. Upon checkout an individual specific script would
reformat the code to that developer's personal preferences.
I guess there's really two aspects to this. One would be allowing
individual specific scripts rather than just project-wide scripts.
Maybe Developer A wants to know some source analysis script on his
check-ins for personal edification. Requiring SCM admin cooperation
often presents an insurmountable burden.
The other is the modification of the checked in code. CVS actually
already does this, it just is opaque and completely non-customizable:
the use of RCS keyword expansion. Why limit it to that? Why not let
the user add in whatever keywords they want. Whatever format they
want. Maybe RCS doesn't cut it for whatever format they are using and
want to roll their own? Maybe they want to run indent on every
check-in.
I don't know if this has been talked about much/at all but thoughts
about how subversion would integrate with defect tracking and project
planning software would be nice. I imagine that might require various
hookage as well, but I'm not sure where. Maybe they are already
covered by the triggers already available.
Justus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:33 2006