We have a massive, ancient codebase that needs a lot of cleanup. We have always had coding standards and everyone has always tried to follow them, but they were not enforced so over time a lot of violations have creeped in. Many of them are just whitespace issues, like using tabs instead of spaces, or spaces where there shouldn’t be any, or missing spaces where they should be. We are going to start actively enforcing our coding standards to make sure more violations don’t creep in, but it’s difficult to enforce them in an automated way on only the changes, so it would be nice to clean up these old files.
There are tools that can automate fixing these issues, however if I do that then blame is going to show me as the owner of those lines, when in reality I may never have even seen them. I know there is a setting to make blame ignore whitespace changes, but I can’t make everyone use blame the same way, including other visual tools and things like gitstats. In an ideal world there would be some way to rewrite history to look like the violations were never introduced, without covering up who introduced the actual code, but I can’t find anything like that.
git filter-branchdoes precisely that.http://git-scm.com/docs/git-filter-branch
This has the same issues as all history rewriting commands do, as it essentially invalidates all cloned repositories.