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

Re: In-depth git blame?

From
Jeff King <peff@peff.net>
Date
Mar 2, 2011, 21:34 UTC
Message-ID
<20110302213437.GG20400@sigill.intra.peff.net>
In-Reply-To
<20110302212951.GB24660@m62s10.vlinux.de>
On Wed, Mar 02, 2011 at 10:29:51PM +0100, Peter Baumann wrote:
Show 9 quoted lines
> > If you use "git gui blame" or "tig blame", both have a "blame from
> > parent commit" feature. This restarts the blame using the content as
> > it was just before the answer you just got, so you can recursively
> > dig.  It's unfortunately a somewhat manual process.
> > 
>  
> Hm. I guess pressing 'B' will blame the parent commit in tig.  But I
> can't figure out how to navigate back to the old commit (before
> pressing 'B')?  Any hints appreciated!

No, it is "," (comma) from the blame viewer in tig to blame starting from the parent of the blamed commit of the highlighted line.

Doing "B" will just re-blame starting at that commit, which will of course give you the same answer (I think it is a global "go to blame view", so it is more useful when you are _not_ in the blame viewer already).

And if you are confused at any point, "h" should give you a context-sensitive list of keystrokes.

-Peff
Previous: Peter BaumannNext: Peter Baumann
Message 4 of 8 in “In-depth git blame?”
  1. JezMar 2, 2011
  2. Jeff KingMar 2, 2011
  3. Peter BaumannMar 2, 2011
  4. Jeff KingMar 2, 2011
  5. Peter BaumannMar 2, 2011
  6. Peter BaumannMar 2, 2011
  7. Jonas FonsecaMar 7, 2011
  8. Peter BaumannMar 8, 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.