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

Re: [PATCH] send-email: add transfer encoding header with content-type

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 21, 2007, 06:58 UTC
Message-ID
<7vbq9ohyox.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20071120125404.GB7998@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 9 quoted lines
>> I think we should add
>> 
>> 	Content-Transfer-Encoding: 8bit
>
> Even though Brian's mail turned out to be hand-generated, this problem
> does exist in git-send-email. I don't know why I didn't add the encoding
> header in the first place, since it is clearly required.
>
> Junio, I think this is maint-worthy.
Yeah, looks good.
Previous: Uwe Kleine-König
Message 9 of 9 in “[BUG] encoding problem with format-patch + send-email”
  1. Uwe Kleine-KönigNov 15, 2007
  2. Jeff KingNov 16, 2007
  3. Uwe Kleine-KönigNov 16, 2007
  4. Junio C HamanoNov 17, 2007
  5. Uwe Kleine-KönigNov 19, 2007
  6. Brian SwetlandNov 19, 2007
  7. send-email: add transfer encoding header with content-typeJeff King, Nov 20, 2007
  8. Uwe Kleine-KönigNov 20, 2007
  9. Junio C HamanoNov 21, 2007

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.