Paul Eggert via tz <tz@iana.org> writes:
There is a tension between having source code that looks nice and consistent now, vs a repository where "git blame" works all the way back to the beginning.
Just in case you weren't already aware of it, there is a Git configuration option intended to help with that: blame.ignoreRevsFile Ignore revisions listed in the file, one unabbreviated object name per line, in git-blame(1). Whitespace and comments beginning with # are ignored. This option may be repeated multiple times. Empty file names will reset the list of ignored revisions. This option will be handled before the command line option --ignore-revs-file. Conventionally, people use a file named .git-blame-ignore-revs at the top level for this purpose. The basic idea is that any whitespace changes go into a separate commit independent of any code changes, and then those commits are added to that file. -- Russ Allbery (eagle@eyrie.org) <https://www.eyrie.org/~eagle/>