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

Effectively tracing project contributions with git

From
JWJoseph Wakeling <joseph.wakeling@webdrake.net>
Date
Sep 12, 2009, 12:30 UTC
Message-ID
<4AAB9459.3070809@webdrake.net>
Hello,

I've recently begun contributing to a FOSS project that has a problem -- although it has extensive git logs (some being CVS/SVN imports) dating back over many years, there has not been maintenance of contribution records on a file-by-file basis.

I'm trying to rectify this and track down who contributed what. Unfortunately while I'm used to basic operations with git, I don't know it well enough to be confident in how to go about tracing contributions in this way.

'git annotate' of course is a nice starting point but of limited use because every time someone tweaks a line (and there have been many such tweaks in the history of the project) the responsibility of the original contributor is replaced by that of the tweaker.

An alternative is to use gitk to trace the history of individual files (or paths, as gitk has it). The problem here is that files have been renamed, content has been moved about between different files and so on.

Finally, there's the option to use gitk to trace contributors (someone has prepared a .mailman file with a complete list of contributors by name and email) and manually or otherwise tally their significant contributions. Again, I'm not sure to what extent this is made difficult by copy/pasting and tweaking of file content.

I'm just hoping that the git community can offer some good advice on this, to what extent the process of tracing contributions can be automated, and so on. I'm not expecting anyone to provide a solution for me, but suggestions and pointers in the possible right directions would be much appreciated.

Thanks & best wishes,
    -- Joe
Next: Jeff King
Message 1 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.