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

66 patches and counting

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Oct 5, 2011, 21:29 UTC
Message-ID
<4E8CCC55.9070408@alum.mit.edu>

My renovation of refs.c [1] is currently at 66 patches and counting. What can I say?: (1) I like to make changes in the smallest irreducible steps and (2) there is a lot that needed to be done in refs.c.

When I'm done, is it OK to dump a patch series like that on the git mailing list? Is it pointless because nobody will review them anyway? Is a big pile of changes like this welcome in any form? Would it be better to convey the changes via git itself (e.g., github) rather than via emails?

Michael
[1] hierarchical-refs at git://github.com/mhagger/git.git
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Next: Junio C Hamano
Message 1 of 8 in “66 patches and counting”
  1. Michael HaggertyOct 5, 2011
  2. Junio C HamanoOct 5, 2011
  3. Jonathan NiederOct 5, 2011
  4. Martin FickOct 6, 2011
  5. Martin FickOct 7, 2011
  6. Michael HaggertyOct 7, 2011
  7. Scalable reference handlingMichael Haggerty, Oct 7, 2011
  8. Martin FickOct 7, 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.