On Tue, 3 May 2011 09:27:28 -0500, Chris Radek wrote: > On Tue, May 03, 2011 at 09:28:43AM +0200, Michael Haberler wrote: >> - reformatting. I know this is a nono, but occasionally source files >> are very hard to read and edit due to formatting and indentation, >> and >> the temptation is high to do that. Beyond the occasional source >> file: >> Can we discuss a 'whitespace reformat day'? > > I am entirely against this. It makes version control work badly > across the change, both for human consumption (viewing patches) and > merges. > > I believe that in no way does the incremental ease of reading > uniformly-formatted code make up for these problems. > > Also I believe that in order to do this we'd need to agree on the > "one > true style" of code, and all such discussions about style and > whitespace are 100% a waste of time.
I agree with you that versioning control across the change breaks history and causes other problems. On the other hand, if you would entertain such a thing it can be accomplished as part of a major revision, and then strict adherence to programming guidelines. The trick would be to develop a working code standard, start using it for new posts and reviews, and then migrate over as part of the next revision. EBo -- ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
