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

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

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Mar 21, 2008, 13:51 UTC
Message-ID
<46a038f90803210651offecf20h9ea527b610c8769f@mail.gmail.com>
In-Reply-To
<7vmyospgz7.fsf@gitster.siamese.dyndns.org>
On Fri, Mar 21, 2008 at 5:24 AM, Junio C Hamano <gitster@pobox.com> wrote:
>  * 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?
How the hell do we spot that one? ;-)
martin
-- 
 martin.langhoff@gmai.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
Previous: Junio C HamanoNext: Johannes Schindelin
Message 3 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.