25 Nov
2009
25 Nov
'09
5:13 p.m.
Ken Thomases wrote:
One important reason to avoid whitespace-only changes is it makes git-blame essentially useless for finding the real source of functional changes.
But is that really important? git-bisect would put you on the other side of any whitespace changes, and a prudent bug-hunter should be referring to the commit logs anyway.
There should be a path to eventual codebase sanity, no matter how slow.
~Nate