From: Jay Soffian <jaysoffian@gmail.com>
To: git <git@vger.kernel.org>
Subject: How to efficiently blame an entire repo?
Date: Thu, 29 Apr 2010 19:12:27 -0400 [thread overview]
Message-ID: <r2l76718491004291612qbe0834ela89f0606e5f477e2@mail.gmail.com> (raw)
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.
The naive solution is to run git blame on all 40K files grep'ing for
the just the authors you want.
Possibly a step up from that is first using log --name-status
--author=... to find just the files which have been touched by those
authors and then blaming only those files.
I guess the next step up would be parsing the diff hunks output by log
-p, but then you're basically re-implementing blame I think.
Am I missing a clever solution?
j.
next reply other threads:[~2010-04-30 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 23:12 Jay Soffian [this message]
2010-04-30 19:45 ` How to efficiently blame an entire repo? Avery Pennarun
2010-04-30 20:16 ` Jay Soffian
2010-04-30 21:21 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=r2l76718491004291612qbe0834ela89f0606e5f477e2@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).