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

Re: [SoC RFC] git statistics - information about commits

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 21, 2008, 09:24 UTC
Message-ID
<7vmyospgz7.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<bd6139dc0803210152o529f3b4fi15c515f5385d8f88@mail.gmail.com>
"alturin marlinon" <alturin@gmail.com> writes:
Show 14 quoted lines
> 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?
Previous: alturin marlinonNext: Martin Langhoff
Message 2 of 12 in “[SoC RFC] git statistics - information about commits”
  1. alturin marlinonMar 21, 2008
  2. Junio C HamanoMar 21, 2008
  3. Martin LanghoffMar 21, 2008
  4. Johannes SchindelinMar 21, 2008
  5. Junio C HamanoMar 22, 2008
  6. alturin marlinonMar 23, 2008
  7. Johannes SchindelinMar 23, 2008
  8. alturin marlinonMar 23, 2008
  9. Johannes SchindelinMar 23, 2008
  10. Junio C HamanoMar 23, 2008
  11. alturin marlinonMar 23, 2008
  12. Jakub NarebskiMar 21, 2008

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.