threads / discuss / 35740

What's with git blame --reverse ?

Subject: What's with git blame --reverse ?

## tl;dr

2 messages between Jan 27, 2014 and Jan 27, 2014.

replies: 1people: 2as markdown or json

David Kastrup· Jan 27, 2014, 12:45 UTC · lore

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.

-- 
David Kastrup

Duy Nguyen· Jan 27, 2014, 14:15 UTC · re: David Kastrup · lore

Re: What's with git blame --reverse ?

On Mon, Jan 27, 2014 at 7:45 PM, David Kastrup <dak@gnu.org> wrote:

Show 8 quoted lines

>
> 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)

-- 
Duy