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

Re: [PATCH 2/2] Add Author and Documentation sections to git-for-each-ref.txt

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 9, 2011, 20:17 UTC
Message-ID
<7voc5k9hfy.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4D773570.4010803@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Just kidding!
>
> (Jeff is the 2nd main f-e-r author, but Junio created it.)
Thanks for bringing this up.

In the very early days (like back when the project was only 12 months old) it made sense to record that this and that command were primarily done by that person. But I don't think it is a good idea anymore.

For example, format-patch was my invention and all the code was mine back when it was a script. Later it was reimplemented in C by Dscho based on my earlier work. But a large part of the actual implementation was done by using the generic revision traversal machinery, whose primary authors back then were Linus and me. The silly original UI design everybody hates ("format-patch <upstream>" is not similar to 'git log <upstream>..'") is "owned" by me, the user facing main() implementation is "owned" by Dscho, and the backend machinery is "owned" by Linus and me.

Who should we list, and more importantly, does it make sense to keep the list up to date as the system evolves?

As the project and the community grew, and also as the internal machinery infrastructure got more modularized, I think ownership at the individual command level has become almost meaningless concept.

Same reasoning applies to the "Documented by". I think it's time for these two sections to go from most (if not all) pages.

Previous: Alexei SholikNext: Jeff King
Message 12 of 24 in “A couple of tweaks in git-for-each-ref.txt”
  1. 0/2 A couple of tweaks in git-for-each-ref.txtAlexei Sholik, Mar 8, 2011
  2. 1/2 Documentation: remove redundant colons in git-for-each-ref.txtAlexei Sholik, Mar 8, 2011
  3. Michael J GruberMar 9, 2011
  4. 2/2 Add Author and Documentation sections to git-for-each-ref.txtAlexei Sholik, Mar 8, 2011
  5. Michael J GruberMar 9, 2011
  6. Alexei SholikMar 9, 2011
  7. Will PalmerMar 17, 2011
  8. Jeff KingMar 17, 2011
  9. Alexei SholikMar 17, 2011
  10. Jeff KingMar 17, 2011
  11. Alexei SholikMar 17, 2011
  12. Junio C HamanoMar 9, 2011
  13. Jeff KingMar 10, 2011
  14. Junio C HamanoMar 10, 2011
  15. Jeff KingMar 11, 2011
  16. Junio C HamanoMar 11, 2011
  17. Alexei SholikMar 12, 2011
  18. Jeff KingMar 13, 2011
  19. Junio C HamanoMar 13, 2011
  20. Jeff KingMar 13, 2011
  21. Junio C HamanoMar 13, 2011
  22. Michael J GruberMar 13, 2011
  23. Jeff KingMar 17, 2011
  24. Junio C HamanoMar 9, 2011

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.