Re: Post Commit Code Formatting

On Thu, 23 Jun 2005, Durfee, Bernard wrote:

> Exploring features and modifications, even if requiring a perceived
> massive change, is crucial to the development of good software. There
> are always design decisions to be made and those decisions should be
> driven by the needs of the user community. Had there been enough
> interest in a more sophisticated two-way communication protocol when SVN
> was early in it's implementation, it may have been very simple to leave
> room for such an enhancement.

Oh, I entirely agree. What I was getting at was that the more I looked
at reformating people's code on commit, the more I decided it was a
really bad idea. That isn't to say that people shouldn't think about
better c/s protocols. I was probably stating things in overly general
terms when talking about something specific.

> > Managing coders really is a different problem, right down to
> > coding style. Either you deal with that, or you don't.
>
> But you wouldn't if you didn't have to.

Very true. Same goes for taxes, expense reports, and visits to the
bathroom. On the other hand, managing all of those things, plus your
coders, *well*, means you can come out ahead of the game.

-j

-- 
Jamie Lawrence                                        jal@jal.org
This is not a novel to be tossed aside lightly. It should be 
thrown with great force.
   - Dorothy Parker
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org