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

Re: Wrap up of Line Level History Browser [long]

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 22, 2010, 20:57 UTC
Message-ID
<AANLkTi=R54C8xQGnPW3VPFnyL+784nG8RMEcHF9s_THD@mail.gmail.com>
In-Reply-To
<201008222247.45600.trast@student.ethz.ch>
Thomas Rast wrote:
Show 9 quoted lines
> 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
[...]
Show 7 quoted lines
> 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!)
Previous: Thomas Rast
Message 3 of 3 in “Wrap up of Line Level History Browser”
  1. Bo YangAug 20, 2010
  2. Thomas RastAug 22, 2010
  3. Jonathan NiederAug 22, 2010

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.