Re: Post Commit Code Formatting

On Wed, 22 Jun 2005, Ben Collins-Sussman wrote:

> In other words, the problem of "make all code nicely formatted" is
> already solvable as a social problem via the pre-commit hook. A lot
> of folks seem to to interpret this as a philosophical war, but it's
> not. If we were writing svn from scratch, we might very well design
> commit to be 'two-way' from the start, knowing what we know now. But
> at this point, few developers think it's worth the bother. Lots of
> work for little benefit.

Which is why most of us consumers of the product, who only seldom (or
don't at all) contribute, shy away from asking for massive changes.

I started out wanting more commit-transforms, but after learning about
the system, I stopped wanting them. The more I looked at the problem,
the more I didn't want to touch it.

Managing coders really is a different problem, right down to coding
style. Either you deal with that, or you don't.

-j, who has ideas without patches, or that much time.

-- 
Jamie Lawrence                                        jal@jal.org
The problem with the global village is all the global village idiots.
  - Paul Ginsparg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org