Brian Behlendorf <brian@collab.net> writes:
> > 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.
>
> That's the wrong layer to implement such a check - better to have a
> development policy that says "run this 'lint' program to make sure your
> code conforms to our coding standards (etc) before every commit", so that
> the developer has a chance to clean things up before it goes in. MHO.
+1
It's one thing to have a layer which rejects a commit because its
improperly indented. It's another to have a layer which reformats the
commit, unbeknownst to the committer, on its way from working copy to
repository. :-) Detection and correction are very different things.
---------------------------------------------------------------------
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