You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
blame: add config options to handle output for ignored lines
When ignoring commits, the commit that is blamed might not be
responsible for the change. Users might want to know when a particular
line has a potentially inaccurate blame. Furthermore, they might never
want to see the object hash of an ignored commit.
This patch adds two config options to control the output behavior.
The first option can identify ignored lines by specifying
blame.markIgnoredFiles. When this option is set, each blame line is
marked with an '*'.
For example:
278b6158d6fdb (Barret Rhoden 2016-04-11 13:57:54 -0400 26)
appears as:
*278b6158d6fd (Barret Rhoden 2016-04-11 13:57:54 -0400 26)
where the '*' is placed before the commit, and the hash has one fewer
characters.
Sometimes we are unable to even guess at what commit touched a line.
These lines are 'unblamable.' The second option,
blame.maskIgnoredUnblamables, will zero the hash of any unblamable line.
For example, say we ignore e5e8d36d04cbe:
e5e8d36d04cbe (Barret Rhoden 2016-04-11 13:57:54 -0400 26)
appears as:
0000000000000 (Barret Rhoden 2016-04-11 13:57:54 -0400 26)
Signed-off-by: Barret Rhoden <[email protected]>
Signed-off-by: Junio C Hamano <[email protected]>
0 commit comments