On Thu, 2009-11-26 at 00:08 +0100, Richard Guenther wrote: > On Thu, Nov 26, 2009 at 12:04 AM, Tom Tromey <tro...@redhat.com> wrote: > >>>>>> "Basile" == Basile STARYNKEVITCH <bas...@starynkevitch.net> writes: > > > > Basile> Of course, not every one has it (notably those working on non-linux > > Basile> systems), but for those who have it, requiring that every C file > > Basile> inside GCC has been automatically indented with GNU indent could > > Basile> help. > > > > I looked at this once. GNU indent doesn't have all the features needed > > to make it correctly support the GCC coding style. I filed a bunch of > > GNU indent bug reports, but AFAIK none of them has ever been fixed. > > > > You could still do this if you didn't mind a coding style change at the > > same time. And of course, this will only help the .c and .h files, not > > everything else. > > Not to mention that I'd find this a quite pointless excercise. I trust > humans much more than the little brain of GNU indent (or whatever > you can code into a reasonable replacement).
I don't think we need to go that far. An SVN pre-commit filter (default on, disabled by SVN attribute if needed) should instead just reject files that have trailing white space. R