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

Re: [PATCH 2/2] send-email: rfc2047-quote subject lines with non-ascii characters

From
Jeff King <peff@peff.net>
Date
Mar 27, 2008, 07:38 UTC
Message-ID
<20080327073808.GA22548@coredump.intra.peff.net>
In-Reply-To
<20080326093310.GA937@coredump.intra.peff.net>
On Wed, Mar 26, 2008 at 05:33:10AM -0400, Jeff King wrote:
Show 6 quoted lines
> No, I have format-patch do the threading. So something like:
> 
>   git format-patch --cover-letter --thread --stdout upstream >mbox
>   mutt -f mbox
> 
> and then in mutt I bind a key to <resend-message>. For each message, I

Since it looks like you are using mutt also, I will warn you that there is a problem with this workflow: when mutt does the resend, it generates a new message-id. Thus the patches are all connected in a thread because they all in-reply-to the cover letter, but the cover letter is not connected, since it has a new message-id.

I'm not sure if there is a way to fix this short of patching mutt. :(
-Peff
Previous: Jeff KingNext: Todd Zullinger
Message 10 of 11 in “send-email: rfc2047-quote subject lines with non-ascii characters”
  1. 2/2 send-email: rfc2047-quote subject lines with non-ascii charactersJeff King, Mar 25, 2008
  2. Teemu LikonenMar 26, 2008
  3. Jeff KingMar 26, 2008
  4. Teemu LikonenMar 26, 2008
  5. Jeff KingMar 26, 2008
  6. Teemu LikonenMar 26, 2008
  7. Teemu LikonenMar 26, 2008
  8. Jeff KingMar 26, 2008
  9. Jeff KingMar 26, 2008
  10. Jeff KingMar 27, 2008
  11. Todd ZullingerMar 27, 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.