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

[BUG] encoding problem with format-patch + send-email

From
Uwe Kleine-König <uwe.kleine-koenig@digi.com>
Date
Nov 15, 2007, 10:57 UTC
Message-ID
<20071115105726.GA18555@bre-cln-ukleine.digi.com>
Hello,
Brian just stumbled over a problem with format-patch + send-email.

format-patch only adds Content-Type and Content-Transfer-Encoding headers iff the body needs it.

send-email adds "From: A. U. Thor <author@tld>" to the body if sender and From: in the patch to send differ.

Both is just fine, but if the author has some non-ascii characters in her name but the body is ascii-only the resulting mail is broken.

What about adding the Content-Type and Content-Transfer-Encoding headers in any case?

Best regards Uwe

-- 
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962
Next: Jeff King
Message 1 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.