Blame

$\DeclareMathOperator{\homop}{Hom} \newcommand{\Hom}[2]{\homop\left(#1,\,#2\right)} \newcommand{\lt}{<} \newcommand{\gt}{>} \newcommand{\amp}{&} \definecolor{fillinmathshade}{gray}{0.9} \newcommand{\fillinmath}[1]{\mathchoice{\colorbox{fillinmathshade}{$\displaystyle \phantom{\,#1\,}$}}{\colorbox{fillinmathshade}{$\textstyle \phantom{\,#1\,}$}}{\colorbox{fillinmathshade}{$\scriptstyle \phantom{\,#1\,}$}}{\colorbox{fillinmathshade}{$\scriptscriptstyle\phantom{\,#1\,}$}}} $

Section 52.8 Blame

The command git blame is simultaneously funny, useful, and powerful. A line of code you do not understand can be traced back to its originating commit. We maintain a list of commits (in .git-blame-ignore-revs) that have no real new code and make just cosmetic changes, so you may want to use this feature. To use:

git blame --ignore-revs-file .git-blame-ignore-revs birds.xml

You can also make this happen every time with a local configuration change, to wit:

git config blame.ignoreRevsFile .git-blame-ignore-revs

To learn more, see Rob Allen’s post

akrabat.com/ignoring-revisions-with-git-blame/

, and Section 50.2.

Prev Top Next