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

Re: [PATCH] include/asm-arm/: Spelling fixes

From
Jeff King <peff@peff.net>
Date
Dec 17, 2007, 23:12 UTC
Message-ID
<20071217231209.GA5558@coredump.intra.peff.net>
In-Reply-To
<20071217230558.GD2105@coredump.intra.peff.net>
On Mon, Dec 17, 2007 at 06:05:58PM -0500, Jeff King wrote:
Show 9 quoted lines
> > I wonder if stripping existing "Message-Id:" away just like we strip
> > away "Date:" from @xh would be a much saner fix.
> 
> That is definitely wrong if we expect to re-use the in-reply-to and
> references headers that already exist (though obviously we could strip
> out all three of those headers and re-add our own).
> 
> I don't have a strong opinion. I never use git-send-email myself, but
> was just trying to fix a reported bug.

Actually, I don't think stripping the message-id is ever the right thing. The user put it in there for some purpose, and "ours not to reason why" (ours but to do and die). IOW, it is not possible for us to know what we are breaking by changing the message-id. It could simply be the reply-to header in the following messages, or it could be the reply-to in some message we have not and will not ever see.

Even if we assume git-send-email only ever gets the unmunged output of git-format-patch, we do not necessarily know it has been fed all of the patches during a single run.

-Peff
Previous: Jeff KingNext: Junio C Hamano
Message 6 of 9 in “Re: [PATCH] include/asm-arm/: Spelling fixes”
  1. J. Bruce FieldsDec 17, 2007
  2. Joe PerchesDec 17, 2007
  3. Jeff KingDec 17, 2007
  4. Junio C HamanoDec 17, 2007
  5. Jeff KingDec 17, 2007
  6. Jeff KingDec 17, 2007
  7. Junio C HamanoDec 17, 2007
  8. Josh TriplettJan 8, 2008
  9. Josh TriplettJan 8, 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.