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

Re: stopping patches from just floating by

From
jidanni@jidanni.org <jidanni@jidanni.org>
Date
Jan 11, 2009, 20:53 UTC
Message-ID
<874p05k1ie.fsf@jidanni.org>
In-Reply-To
<alpine.LNX.1.00.0901111524110.19665@iabervon.org>

I see. Say, for my forthcoming 40 minor grammar fixes that affect 20 files in Documentation/*, I just couldn't bear spamming this list with more that one or two [PATCH] mails. OK one long mail it will be then, with several commits encompassing many diffs. Hope that will be OK. (Then another long mail next month, when I finish looking at the second half of the man pages.)

Previous: Daniel BarkalowNext: Junio C Hamano
Message 3 of 7 in “stopping patches from just floating by”
  1. jidanni@jidanni.orgJan 11, 2009
  2. Daniel BarkalowJan 11, 2009
  3. jidanni@jidanni.orgJan 11, 2009
  4. Junio C HamanoJan 11, 2009
  5. grammar patches not best use of talentjidanni@jidanni.org, Jan 12, 2009
  6. jdelstrother@gmail.comJan 12, 2009
  7. Junio C HamanoJan 12, 2009

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.