From: Jeff King <peff@peff.net>
Date: Wed, 02 Mar 2011 21:15:45 GMT
Subject: Re: In-depth git blame?
Message-ID: <20110302211545.GD20400@sigill.intra.peff.net>
In-Reply-To: <AANLkTi=694NiUMzcHkNZ09sotcoN+=wPMnxnom5_ex+f@mail.gmail.com>

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.

There was a GSoC project to do what you asked, where you would indicate
a set of lines and get a "git log"-like output of all the commits
touching those lines. But there were some issues with the code, and it
never quite made it upstream, I think. I'm not sure what the current
status is. Cc'ing Thomas and Bo, who worked on it.

-Peff