Hear, hear. I have absolutely no interest in "accurate history". WHY. Do people really want to see my minor spelling mistakes and goofs that got corrected in

Hear, hear. I have absolutely no interest in "accurate history". WHY. Do people really want to see my minor spelling mistakes and goofs that got corrected in review? It's worth spending the extra time to have a completely clean and perfect log, if only for being able to read your commit history like a novel, but also for using `bisect` to find regressions and behavior changes. --- I have gone to extremes. At some point this summer, I realized that running the tests with one collection of flags led to breakage, and this breakage had been there for almost two months, and it was important that this flag work. (Yes, it was also a testing/CI issue, and we fixed that.) I found the issue with `git bisect` and then patched that change two months ago and rebased everything - a couple of hundred commits. We all feel it is of key importance that all the tests pass at each commit ID, so no one had any issues with that and it really didn't take very long. To rebase without changing modification dates, use `git -c rebase.instructionFormat='%s%nexec GIT_COMMITTER_DATE="%cD" git commit --amend --no-edit' rebase -i`