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

Re: `git-send-email' doesn't specify `Content-Type'

From
Brian Swetland <swetland@google.com>
Date
Nov 11, 2007, 08:39 UTC
Message-ID
<20071111083915.GA18021@bulgaria>
In-Reply-To
<20071111083224.GA30299@sigill.intra.peff.net>
This issue with the encoding of the author got me thinking...

What happens if the metadata has utf8 content and the patch itself has some *other* non-ascii encoding (some iso-latin variant perhaps).

Is there any way to deal with that situation sanely other than indicate that it's 8bit content and not specify an encoding? Is that what happens currently?

Brian
Previous: Jeff KingNext: Jeff King
Message 9 of 13 in “`git-send-email' doesn't specify `Content-Type'”
  1. Ludovic CourtèsNov 10, 2007
  2. Johannes SchindelinNov 10, 2007
  3. Brian SwetlandNov 10, 2007
  4. Björn SteinbrinkNov 10, 2007
  5. Brian SwetlandNov 10, 2007
  6. Björn SteinbrinkNov 10, 2007
  7. Jeff KingNov 11, 2007
  8. Jeff KingNov 11, 2007
  9. Brian SwetlandNov 11, 2007
  10. Jeff KingNov 11, 2007
  11. Brian SwetlandNov 11, 2007
  12. Jeff KingNov 11, 2007
  13. Jeff KingNov 11, 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.