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

Content-Type handling

From
TATomas Cohen Arazi <tomascohen@gmail.com>
Date
Sep 17, 2012, 16:34 UTC
Message-ID
<CABZfb=UhKRREMG_XNJHDJHwbwroi5TKWwgQH-Ge1BDJETizG2Q@mail.gmail.com>
Hi, I'm not sure it is a bug, but we used:
git config --global format.headers "Content-Type: text/plain; charset=\"utf-8\""

and recently (perhaps an Ubuntu default setup issue) the content-type is being automatically set, the result is that patches contain this:

Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
This might not be the problem, but when I apply the patch I get this:
fatal: cannot convert from UTF-8utf-8 to UTF-8

which looks like a bug. Not sure it hasn't been reported before, but I think it should take one of the content-type specifications and not append both. I couldn't find a place to looks for previous bug reports to check, so forgive me if this is not the right place to report it.

Regards To+

Next: Junio C Hamano
Message 1 of 3 in “Content-Type handling”
  1. Tomas Cohen AraziSep 17, 2012
  2. Re*: Content-Type handlingJunio C Hamano, Sep 17, 2012
  3. mailinfo: do not concatenate charset= attribute values from mime headersJunio C Hamano, Sep 17, 2012

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.