From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Joseph Wakeling <joseph.wakeling@webdrake.net>, git@vger.kernel.org
Subject: Re: Effectively tracing project contributions with git
Date: Sat, 12 Sep 2009 21:03:35 +0200 [thread overview]
Message-ID: <fabb9a1e0909121203r527bc81ctd68382fc1107bf06@mail.gmail.com> (raw)
In-Reply-To: <20090912185940.GA21277@coredump.intra.peff.net>
Heya,
On Sat, Sep 12, 2009 at 20:59, Jeff King <peff@peff.net> wrote:
> I think it is less a git problem and more of a "how do you want to
> define contribution" problem. The above is just my thinking about it for
> a few minutes. Sverre Rabelier (cc'd) did a "git stats" GSoC project
> last year, but I don't think I ever looked closely at the results or
> what metrics he came up with. But that is probably a good direction to
> look in.
Git stats can aggregate diffs, so it can show you "this author made
changes to this many lines to this file in total", but it doesn't work
across renames. It also has an option to aggregate that to a total per
project number, but I'm not sure how useful that is to your case, as
you seem to be interested in a per-file/line basis? I agree with Jeff
that you'll need to define more precisely what it is you want to know
:).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-09-12 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 12:30 Effectively tracing project contributions with git Joseph Wakeling
2009-09-12 18:59 ` Jeff King
2009-09-12 19:03 ` Sverre Rabbelier [this message]
2009-09-13 0:10 ` Joseph Wakeling
2009-09-13 2:28 ` Theodore Tso
2009-09-13 9:24 ` Jeff King
2009-09-13 14:30 ` Joseph Wakeling
2009-09-13 0:03 ` Joseph Wakeling
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=fabb9a1e0909121203r527bc81ctd68382fc1107bf06@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=joseph.wakeling@webdrake.net \
--cc=peff@peff.net \
/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).