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

Re: Effectively tracing project contributions with git

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Sep 12, 2009, 19:03 UTC
Message-ID
<fabb9a1e0909121203r527bc81ctd68382fc1107bf06@mail.gmail.com>
In-Reply-To
<20090912185940.GA21277@coredump.intra.peff.net>
Heya,
On Sat, Sep 12, 2009 at 20:59, Jeff King <peff@peff.net> wrote:
Show 6 quoted lines
> 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
Previous: Jeff KingNext: Joseph Wakeling
Message 3 of 8 in “Effectively tracing project contributions with git”
  1. Joseph WakelingSep 12, 2009
  2. Jeff KingSep 12, 2009
  3. Sverre RabbelierSep 12, 2009
  4. Joseph WakelingSep 13, 2009
  5. Theodore TsoSep 13, 2009
  6. Jeff KingSep 13, 2009
  7. Joseph WakelingSep 13, 2009
  8. Joseph WakelingSep 13, 2009

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.