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

Re: How to efficiently blame an entire repo?

From
Avery Pennarun <apenwarr@gmail.com>
Date
Apr 30, 2010, 19:45 UTC
Message-ID
<x2s32541b131004301245o46d8e855va0b51ebce279398b@mail.gmail.com>
In-Reply-To
<r2l76718491004291612qbe0834ela89f0606e5f477e2@mail.gmail.com>
On Thu, Apr 29, 2010 at 7:12 PM, Jay Soffian <jaysoffian@gmail.com> wrote:
Show 7 quoted lines
> Let's say you've got a repo with ~ 40K files and 35K commits.
> Well-packed .git is about 800MB.
>
> You want to find out how many lines of code a particular group of
> individuals has contributed to HEAD.
>[...]
> Am I missing a clever solution?

How often do you need to do this? If it's just once in your life, then the brute force solution of just letting 'git blame' grind through it for a few hours is probably the cleverest :)

Have fun,
Avery
Previous: Jay SoffianNext: Jay Soffian
Message 2 of 4 in “How to efficiently blame an entire repo?”
  1. Jay SoffianApr 29, 2010
  2. Avery PennarunApr 30, 2010
  3. Jay SoffianApr 30, 2010
  4. Jeff KingApr 30, 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.