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

Re: [PATCH] post-receive-email: Set content-type and encoding in generated mail

From
Jeff King <peff@peff.net>
Date
Jul 31, 2009, 01:52 UTC
Message-ID
<20090731015215.GC11392@coredump.intra.peff.net>
In-Reply-To
<20090730080206.GR31428@hebe.informatik.RWTH-Aachen.DE>
On Thu, Jul 30, 2009 at 10:02:06AM +0200, Fabian Emmes wrote:
> thanks Teemu and Jeff for correcting the errors. Indeed I assumed that
> git log would always output UTF-8 and a "Content-Type" header would be
> valid on its own. The patch of Jeff solves my problem. I tested the
> results in mutt, kmail and thunderbird.

Great. Would you mind re-submitting the patch you tested with a proper write-up in the commit message?

-Peff
Previous: Fabian Emmes
Message 5 of 5 in “post-receive-email: Set content-type and encoding in generated mail”
  1. post-receive-email: Set content-type and encoding in generated mailFabian Emmes, Jul 29, 2009
  2. Teemu LikonenJul 29, 2009
  3. Jeff KingJul 29, 2009
  4. Fabian EmmesJul 30, 2009
  5. Jeff KingJul 31, 2009

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.