> On Wed, 25 Nov 2009, Dave Korn wrote: >> Joseph S. Myers wrote: >> > Doing it right at the end of branch-to-trunk merges for a release >> (which >> > is where we are right now, just after merges from Graphite) is >> probably >> > the optimal timing in terms of minimising the amount of branches that >> will >> > need fixing up. The problem is doing it without warning or consensus. >> >> Yep. Given that, maybe we should make a global whitespace cleanup an >> official part of the release branching process? It would be nice to >> keep it >> from all building up again, and we could avoid the pain if it was >> regular and >> predictable. > > What is the _point_ in doing this? Is there _any_ positive effect > of removing trailing whitespace? Does it looks like there are no bugs to > fix in gcc so that the pointless task of removing trailing whitespace > looks appealing??
Gentlemen, a point of order please. Many people read these lists and we place high regard on the quality of the GCC project as well as the people involved. A personal slight as well as an error may happen from time to time but this is simply the nature of working as a software engineer. Let us not degrade into a base argument with words traded and thus undermine the great name that GCC and open source has. I am sure that this issue can be resolved without any damage done to the most precious resource we have, good people that work together openly and with respect and dignity. Having said that, I firmly would defend any of you as truely awesome engineers and good people that work to benefit the state of mankind. -- Dennis Clarke http://www.blastwave.org/ dcla...@opensolaris.ca <- Email related to the open source Solaris dcla...@blastwave.org <- Email related to open source for Solaris
