![]() ![]() This differs from -S rev-list, which specifies the list of commits to process for the blame. I'd like to be able to ignore Y: both the existence of the commit as well as any changes it made. (Merged by Junio C Hamano - gitster - in commit 209f075, ) blame: add the ability to ignore commits and their changesĬommits that make formatting changes or function renames are often not interesting when blaming a file.Ī user may deem such a commit as 'not interesting' and want to ignore and its changes it when assigning blame.įor example, say a file has the following git history / rev-list: -O-A-X-B-C-D-Y-E-FĬommits X and Y both touch a particular line, and the other commits do not: X: "Take a third parameter" See commit f0cbe74, commit a07a977 (), and commit 1fc7338, commit 8934ac8, commit ae3f36d, commit 55f808f, commit f93895f, commit 24eb33e () by Barret Rhoden ( brho). See commit 07a54dc () by Jeff King ( peff). See commit 78fafbb (), and commit 1d028dc () by Michael Platings (``). " git blame" learned to " ignore" commits in the history, whose effects (as well as their presence) get ignored.Īnd you can register that in your git config! You don't even need to pass those commits in parameters on every git blame call. That being said, git blame can now ignore commits (even maybe not in this particular case). Unfortunately both removing and adding a file are quite drastic changes so -ignore-rev won't help here. Git blame -ignore-rev works on the assumption that the specified commit made an uninteresting change (e.g. ![]() (IntelliJ "annotate" feature might take a while before catching up) Has anybody ever fixed this problem before without rewriting history?īut with Git 2.23, you will be able to instruct git blame to ignore those two problematic commits. These two commits make me sad whenever I use the Annotate feature in IntelliJ (which is basically git blame). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |