Tue 27 Mar 2012 07:22:24 AM UTC, comment #2:
Each change covers other changes all the time, and this does not mess with git, if you want to dig deeper, you just need to specify revision, to uncover earlier changes.
Of course in this case, many lines will be changed and probably you will need to specify revision with git blame more often (and this adds some inconvenience), but sooner it will be re-factored, sooner it will be covered by new changes and such inconvenience simply disappears.
By the way (I'm mercurial user), but found in git-blame manual -w switch - "Ignore whitespace when comparing the parent's version and the child's to find where the lines came from.". So I guess this switch can completely resolve this problem.
So think, how much you use git blame and how much it annoys other possible contributors, that tries to hack some thing in such code.
In configuration files, that I copied with --copy-config=all, I already replaced all tabs to spaces and all "from foo import *", since such imports confuse my pyflakes and syntastic error checkers in vim, making them unusable, since there is no way to track undefined name errors at all.
|