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

Re: In-depth git blame?

From
PBPeter Baumann <waste.manager@gmx.de>
Date
Mar 2, 2011, 21:29 UTC
Message-ID
<20110302212951.GB24660@m62s10.vlinux.de>
In-Reply-To
<20110302211545.GD20400@sigill.intra.peff.net>
On Wed, Mar 02, 2011 at 04:15:45PM -0500, Jeff King wrote:
Show 11 quoted lines
> On Wed, Mar 02, 2011 at 03:43:42PM -0500, Jez wrote:
> 
> > Git-blame is useful, but sometimes I want to know the series of
> > commits that have affected a line -- not just the most recent one. Is
> > there a way to do this?
> 
> 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!
-Peter
Previous: Jeff KingNext: Jeff King
Message 3 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.