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

Re: Check out git-author

From
Jeff King <peff@peff.net>
Date
Sep 8, 2014, 05:19 UTC
Message-ID
<20140908051956.GA8987@peff.net>
In-Reply-To
<0a3b0f232ec56517d4db43c6bd6ebb63@cs.wisc.edu>
On Sun, Sep 07, 2014 at 06:05:13PM -0500, xmeng wrote:
Show 9 quoted lines
> The problem with git-blame is that it only reports the last author/commit
> that changed the line, regardless of the magnitude of the change. Sometimes,
> the last author may only change a tiny part of the code and should not be
> blamed. I developed a built-in tool called "git-author" to address this
> problem. Git-author is designed to track the complete development history of
> a line. For the same line of code:
> 
> $ git author -c -L 2235,2235 fs/ext4/mballoc.c
> [...]

Have you tried "git log -L 2235,2235:fs/ext4/mballoc.c -- fs/ext4/mballoc.c"? Can you compare your approach to that of "log -L"?

-Peff
Previous: xmengNext: Torsten Bögershausen
Message 2 of 3 in “Check out git-author”
  1. xmengSep 7, 2014
  2. Jeff KingSep 8, 2014
  3. Torsten BögershausenSep 8, 2014

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.