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

Re: [RFC] Use cases for 'git statistics'

From
Jakub Narebski <jnareb@gmail.com>
Date
May 12, 2008, 12:40 UTC
Message-ID
<200805121440.12836.jnareb@gmail.com>
In-Reply-To
<bd6139dc0805120449j874e4b8j21b90f79230e45a7@mail.gmail.com>
Sverre Rabbelier wrote:
> On Mon, May 12, 2008 at 1:19 PM, Jakub Narebski <jnareb@gmail.com> wrote:
Show 6 quoted lines
> >  * Maintainer: how close should I examine provided patch?
> 
> I'm not sure I understand what you mean with this, perhaps related to
> "Name: Finding parts of the content in which a lot of bugs are
> introduced and fixed" (e.g., patches to bug prone areas should be
> examined more closely).

This is, IMHO, the most complex example (at least to do properly). It begins with: does given author have code touching given subsystem (i.e. is it for him/her new contribution wrt. subsystem)? How many commits he/she has affecting given subsystem? How often he/she rewrites code? How many bugs were introduced?

Details I think need to be provided by maintainer...
Show 5 quoted lines
> >  * Contributor: what happened with my code?
> 
> Do you mean a "track my code" like feature? Showing the movement of a
> particular piece of code through the code? (Displaying information
> like "moved from foo.c to bar.c in commit 0123456789abcd"?)
I was thinking there about "git blame --reverse".
Show 5 quoted lines
> >  * Searching where to contribute: what are oldest part of code dealing
> >   with error messages (find ancient code)?
> 
> In other words, find the lines with the oldest modification time stamp
> from 'git blame'?

Or find the lines with oldest modification stamp with "die" or "warn", or find which messages are oldest, even if wrapper have changed.

P.S. I wonder how hard to be to plug-in such SCM statistic system
into something like project management, see
  "Joel On Software: Evidence based scheduling" (of programming tasks)
  http://www.joelonsoftware.com/items/2007/10/26.html
-- 
Jakub Narebski
Poland
Previous: Sverre RabbelierNext: Sverre Rabbelier
Message 7 of 16 in “[RFC] Use cases for 'git statistics'”
  1. Sverre RabbelierMay 8, 2008
  2. Sverre RabbelierMay 12, 2008
  3. Jakub NarebskiMay 12, 2008
  4. Sverre RabbelierMay 12, 2008
  5. Jakub NarebskiMay 12, 2008
  6. Sverre RabbelierMay 12, 2008
  7. Jakub NarebskiMay 12, 2008
  8. Sverre RabbelierMay 12, 2008
  9. Jakub NarebskiMay 13, 2008
  10. Sverre RabbelierMay 13, 2008
  11. Jakub NarebskiMay 14, 2008
  12. Andreas EricssonMay 15, 2008
  13. Junio C HamanoMay 17, 2008
  14. Sverre RabbelierMay 18, 2008
  15. Junio C HamanoMay 21, 2008
  16. Sverre RabbelierMay 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.