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

What's with git blame --reverse ?

From
David Kastrup <dak@gnu.org>
Date
Jan 27, 2014, 12:45 UTC
Message-ID
<87y5218ufn.fsf@fencepost.gnu.org>

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
Next: Duy Nguyen
Message 1 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.