My vote would be to add it in the commit hook. There should be no disadvantages that way and
formatting will get better over time. Heavily worked sections of code will come up to date quickly while
less busy sections of code (in terms of changes) may never come up to speed. At least things
won't get any worse over time.

On Dec 3, 2010 12:27am, Tim Kroeger <tim.kroeger@cevis.uni-bremen.de> wrote:
> On Thu, 2 Dec 2010, Roy Stogner wrote:
>
>
>
> > This hurts the usefulness of "svn blame".  Whoever commits the first
>
> > massive set of astyle changes suddenly looks responsible for a whole
>
> > lot of code where he merely touched whitespace.
>
> >
>
> > This hurts the usefulness of "svn diff -r A:B" where A is any revision
>
> > number before the whitespace change and B is any revision number
>
> > after.
>
>
>
> To me, this seems like a severe drawback, so I would vote against
>
> astyle (if you are interested in my opinion...).
>
>
>
> Actually, I do not see any essential benefit from gettig rid of
>
> spurious whitespace, with the one possible exception of TAB
>
> characters, because those tend to expand to a different number of
>
> spaces in some editors, in particular editors on bizarre operating
>
> systems like MS Windows.
>
>
>
> Best Regards,
>
>
>
> Tim
>
>
>
> --
>
> Dr. Tim Kroeger
>
> CeVis -- Center of Complex Systems and Visualization
>
> University of Bremen              tim.kroeger@cevis.uni-bremen.de
>
> Universitaetsallee 29             tim.kroeger@mevis.fraunhofer.de
>
> D-28359 Bremen                             Phone +49-421-218-7710
>
> Germany                                    Fax   +49-421-218-4236
>
>
>
> ------------------------------------------------------------------------------
>
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
>
> Tap into the largest installed PC base & get more eyes on your game by
>
> optimizing for Intel(R) Graphics Technology. Get started today with the
>
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
>
> http://p.sf.net/sfu/intelisp-dev2dev
>
> _______________________________________________
>
> Libmesh-devel mailing list
>
> Libmesh-devel@lists.sourceforge.net
>
> https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>