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

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

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 21, 2008, 13:56 UTC
Message-ID
<alpine.LSU.1.00.0803211455550.4124@racer.site>
In-Reply-To
<46a038f90803210651offecf20h9ea527b610c8769f@mail.gmail.com>
Hi,
On Fri, 21 Mar 2008, Martin Langhoff wrote:
Show 5 quoted lines
> 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? ;-)

It would probably involve finding pieces of code that were changed multiple times, i.e. lines of code that did not survive for many commits.

Ciao, Dscho

Previous: Martin LanghoffNext: Junio C Hamano
Message 4 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.