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

Re: 66 patches and counting

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 5, 2011, 21:36 UTC
Message-ID
<7vty7n5dfi.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4E8CCC55.9070408@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
> When I'm done, is it OK to dump a patch series like that on the git
> mailing list?
Bits and pieces that are of digestable sizes.

I would wait sending anything large-ish (like more than 10 patches) before 'next' is rewound, which is the sign the cycle is in full swing.

> Is it pointless because nobody will review them anyway?
Bits and pieces that are of digestable sizes. Especially given:
> I like to make changes in the smallest irreducible steps

each step in your series should make sense by itself already (otherwise you would have rebase-i'ed them to collapse too-small pieces into one that makes sense standalone on top of the earlier steps).

> Is a big pile of changes like this welcome in any form?
Bits and pieces that are of digestable sizes.
Previous: Michael HaggertyNext: Jonathan Nieder
Message 2 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.