3 ms·
Have you run into issues where the "let's reformat the entire codebase" commit makes `git blame` unusable?
by philwelch 8y ago
Have you run into issues where the "let's reformat the entire codebase" commit makes `git blame` unusable?
- ambivalence 8y agoIt doesn't. Use `git hyper-blame` or `git blame $REV^ -- $PATH`. Sure, there is an additional step but we feel this shouldn't be a blocker for significant workflow improvements. In fact, a single big "reformat all" commit is better than a bunch of incremental ones that reformat areas that you also change semantically. That is harder to filter and makes diffs harder to follow (which changes are logic and which are just style?).
- sciurus 8y agoI hadn't head of hyper-blame before. It's part of chromium's depot_tools. > git hyper-blame is like git blame but it can ignore or "look through" a given set of commits, to find the real culprit. https://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/git-hyper-blame.html https://commondatastorage.googleapis.com/chrome-infra-docs/f...