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

Re: blame --reverse selecting wrong commit

From
Junio C Hamano <gitster@pobox.com>
Date
May 30, 2011, 06:47 UTC
Message-ID
<7vlixoofaj.fsf@alter.siamese.dyndns.org>
In-Reply-To
<BANLkTimXppE9sCW8tMntbD8p5-bRVFLHmQ@mail.gmail.com>
Shawn Pearce <spearce@spearce.org> writes:
> Rereading commit 85af7929ee ("git-blame --reverse"), it seems you left
> this an "exercise for the reader"... and in the past 3 years, no
> reader has stepped forward to implement the exercise as a patch to
> blame. *sigh*
Yeah.

It has always been my opinion that asking for "one commit past the blamed one" is a undefined request (after all, blame for the line fell on that commit exactly why the next commit does _not_ have any corresponding line), so that is why I punted there.

Now we seem to have found one interested reader, eh? ;-)
Previous: Shawn PearceNext: Shawn Pearce
Message 4 of 6 in “blame --reverse selecting wrong commit”
  1. Shawn PearceMay 30, 2011
  2. Shawn PearceMay 30, 2011
  3. Shawn PearceMay 30, 2011
  4. Junio C HamanoMay 30, 2011
  5. Shawn PearceMay 30, 2011
  6. Junio C HamanoMay 30, 2011

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.