Skip to contentSkip to conversation

What's with git blame --reverse ?

DISCUSSION David Kastrup 2 participants 2 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

The git blame manual page talks about using git blame --reverse to figure out when a particular change disappeared, but I cannot make it produce anything useful regardless of what range I give it. Using --root delivers a different state of uselessness.

Can anyone give a recipe for using git blame --reverse on the Git code base for figuring out anything of relevance?

Since I am in the process of rewriting git-blame, of course I want to verify that everything works, but while I achieve the same results, they seem fabulously useless before and after my rewrite.

Signature · 1 line
David Kastrup
#1 lore raw
Quoted 8 lines · David Kastrup

The git blame manual page talks about using git blame --reverse to figure out when a particular change disappeared, but I cannot make it produce anything useful regardless of what range I give it. Using --root delivers a different state of uselessness.

Can anyone give a recipe for using git blame --reverse on the Git code base for figuring out anything of relevance?

I rarely use blame, but the commit that introduces --reverse seems to have an example. See 85af792 (git-blame --reverse - 2008-04-02)

Signature · 1 line
Duy