git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "alturin marlinon" <alturin@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [SoC RFC] git statistics - information about commits
Date: Fri, 21 Mar 2008 02:24:28 -0700	[thread overview]
Message-ID: <7vmyospgz7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <bd6139dc0803210152o529f3b4fi15c515f5385d8f88@mail.gmail.com> (alturin marlinon's message of "Fri, 21 Mar 2008 09:52:38 +0100")

"alturin marlinon" <alturin@gmail.com> writes:

> My plan for this summer is to create a 'statistics' feature for git.
>
> It would provide the following functionality:
> * Show how many commits a specific user made.
> * Show the (average) size of their changes (in lines for example).
> * Show a 'total diff', that is, take the difference between the source
> with, and without their changes, including its size (with for example
> a -c switch).
> * Show which contributors have contributed to the part of the code
> that a patch modifies.
> * Show what part of the code a maintainer is working on the most.
> * Define an output format for this information that can be used by
> other tools (such as gitk and git-web)
> * (Optional) Integrate all this information with gitk and git-web.

* Within reasonable amount of time suitable for interactive use, if you
  intend it to work with gitk.

What's the ballpack performance goal for e.g. post 2.6.12 kernel history
which is about 85k commits, 3800 authors, 24k files?

* Who contributed the most code that needed the many fix-ups on top?

* Which part of the codebase had the most commits that had "oops, screwed
  up, I am fixing this but this is a tricky code" fixes?

  reply	other threads:[~2008-03-21  9:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21  8:52 [SoC RFC] git statistics - information about commits alturin marlinon
2008-03-21  9:24 ` Junio C Hamano [this message]
2008-03-21 13:51   ` Martin Langhoff
2008-03-21 13:56     ` Johannes Schindelin
2008-03-22 19:40   ` Junio C Hamano
2008-03-23 14:07     ` alturin marlinon
2008-03-23 14:28       ` Johannes Schindelin
2008-03-23 15:41         ` alturin marlinon
2008-03-23 16:32           ` Johannes Schindelin
2008-03-23 17:31       ` Junio C Hamano
2008-03-23 21:32         ` alturin marlinon
2008-03-21 14:49 ` Jakub Narebski

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=7vmyospgz7.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=alturin@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).