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

Re: git blame --reverse doesn't find line in HEAD

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 6, 2017, 17:22 UTC
Message-ID
<xmqqh8t3hiuq.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CA+SQVf24rcQ1iKAQBW0Ky7Qm8zuF3Esw8qMKvG+KCbCA-mCcfA@mail.gmail.com>
Nick Snyder <nick@sourcegraph.com> writes:
> This can be reproduced on Linux and Mac. This behavior seems to be a bug.
Can you bisect to see when the feature stopped working as you expect?

Unlike a forward blame, where the command tries to find a commit that is responsible for a line being in the final result (i.e. typically, HEAD), a reverse blame is not about finding a commit that is responsible for a line (that used to be in the oldest commit) not being in a more recent codebase. It finds up to which commit each line survived without getting touched since the oldest commit in the range.

Previous: Nick SnyderNext: Nick Snyder
Message 3 of 5 in “git blame --reverse doesn't find line in HEAD”
  1. Nick SnyderNov 29, 2017
  2. Nick SnyderDec 6, 2017
  3. Junio C HamanoDec 6, 2017
  4. Nick SnyderDec 6, 2017
  5. Nick SnyderDec 7, 2017

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.