Creating a Proper Path for Clean-up Patches
Posted May 29, 2008 6:01 UTC (Thu) by midg3t
In reply to: Creating a Proper Path for Clean-up Patches
Parent article: Getting the right kind of contributions
I think the point is that whitespace-only changes at any time are noise. Trying to understand annotated code (a la
git blame) that is punctuated with whitespace-only changes is a waste of time. The preferable method is to fix the whitespace when you are making a code change on the same line (or block). That way every change has a purpose as a code change and doesn't get in the way when looking at the code history.
Keeping whitespace changes in a separate tree sounds OK on paper, but in practice it means someone has to spend all day resolving conflicts between code changes and whitespace changes. Not fun.
to post comments)