From: Jonathan Nieder <jrnieder@gmail.com>
Date: Sun, 22 Aug 2010 20:57:06 GMT
Subject: Re: Wrap up of Line Level History Browser [long]
Message-ID: <AANLkTi=R54C8xQGnPW3VPFnyL+784nG8RMEcHF9s_THD@mail.gmail.com>
In-Reply-To: <201008222247.45600.trast@student.ethz.ch>

Thomas Rast wrote:

> For me it replaces a manual iterative process to find out in what ways
> a function was patched until it came to have its current shape:
>
>  git-blame the area, find the most recent commit C
>  while 1:
>    git show C
>    if that explains the code: break
>    git-blame the area in C^
>    find the most recent commit and call it C again
[...]
> All of this can now be replaced by a simple
>
>  git log -L <range> <filename>
>
> A good example that I did a lot of testing with:
>
>  git log --graph be58e70d^ -L /builtin_funcname_pattern/,/^}/ diff.c

Thanks. (And thanks to Bo for implementing it!)