git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Duy Nguyen <pclouds@gmail.com>
Date
Jan 27, 2014, 14:15 UTC
Message-ID
<CACsJy8CCZxKYW=AAz-OsKxrjNo2NyqUQF=NJXH20hv4miFUs8g@mail.gmail.com>
In-Reply-To
<87y5218ufn.fsf@fencepost.gnu.org>
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
Previous: David Kastrup
Message 2 of 2 in “What's with git blame --reverse ?”
  1. David KastrupJan 27, 2014
  2. Duy NguyenJan 27, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.