We somewhat recently implemented commit hooks on our repository that force no trailing whitespace (ie, reject a commit if it has trailing whitespace). I thought it was going to be draconian at first... But I actually like it a lot because it keeps out a _bunch_ of superfluous diffs.
We just use some Emacs rules that automatically delete trailing whitespace... and a small Perl script that others can use before checking in. Something to consider.... Sent from my iPhone On Dec 2, 2011, at 2:33 PM, Roy Stogner <[email protected]> wrote: > > Regularizing whitespace (e.g. deleting trailing whitespace from lines, > fixing formatting that doesn't fit the rest of the file) is great, but > it tends to generate enormous diffs, so when simultaneously changing > whitespace and features, let's keep them in separate svn commits, > please. > > Having to hunt through a 600-line diff to review the 100 lines of > actual substance is an unnecessarily needle-in-a-haystack task. > --- > Roy > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Libmesh-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-devel ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
