Re: Is there any efficient way to track history of a piece of code?

From: Jeff King <peff@peff.net>
Date: May 8, 2014, 07:00 UTC
Message-ID: <20140508070051.GA4532@sigill.intra.peff.net>
In-Reply-To: <CAHz2CGW4rRWzGMPxM1XsoYvrwrrddrxAr+AKAi5SdMx+3rBjNg@mail.gmail.com>

On Thu, May 08, 2014 at 02:54:56PM +0800, Jianyu Zhan wrote:

Show 15 quoted lines

> Usually, a trivial change(like coding style fix) may bury a
> original change of the code, and thus git blame is of less
> help. And to address this situation, I have to do like this:
> 
>    git blame -s REF^ <file-in-question> > temp
> 
> to dig into the history recursively by hand, to find out
> the original change.
> 
> Here, REF is commit-id that git blame reports.
> 
> git log -L is a good alternative option, but sometimes it seems
> too cubersome, as I care only one line of code.
> 
> Is there any current solution or suggestion?

Try "tig blame"[1]; from the blame view, the "," command will restart the blame at REF^ automatically. If you don't mind a more graphical interface, I think "git gui blame" can also reblame from the parent from the right-click context menu.

-Peff

[1] http://jonas.nitro.dk/tig/