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
Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
Date
Nov 20, 2007, 13:49 UTC
Message-ID
<20071120134934.GA546@informatik.uni-freiburg.de>
In-Reply-To
<20071120125404.GB7998@sigill.intra.peff.net>
Hello,
Jeff King wrote:
Show 7 quoted lines
> We add the content-type header only when we have non-7bit
> characters from the 'From' header, so we really need to
> specify the encoding (in other cases, where the commit text
> needed a content-type, git-format-patch will already have
> added the encoding header).
> 
> Signed-off-by: Jeff King <peff@peff.net>
Acked-by: Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
-- 
Uwe Kleine-König

$ dc << EOF
[d1-d1<a]sa99d1<a1[rdn555760928P*pz1<a]salax
EOF
Previous: Jeff KingNext: Junio C Hamano
Message 8 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.