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

Re: [PATCH v2] post-receive-email: explicitly set Content-Type header

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Sep 20, 2011, 09:32 UTC
Message-ID
<4E785DC6.80105@viscovery.net>
In-Reply-To
<1316506023-5098-1-git-send-email-zapped@mail.ru>
Am 9/20/2011 10:07, schrieb Alexey Shumkin:
Show 5 quoted lines
> Some email clients (e.g. claws-mail) incorrectly display
> message body when there is no Content-Type header and charset
> explicitly defined.
> So, set explicitly Content-Type header and charset
> can be defined with hooks.emailcharset config variable.

Please write full sentences with complete punctuation and capitalization. Perhaps you meant to say:

  Some email clients (e.g. claws-mail) display the message body
  incorrectly when the charset is not defined explicitly in a
  Content-Type header. Insert a Content-Type header in the message.
  The charset can be defined with the config variable
  hooks.emailcharset.
> +# hooks.emailcharset
> +#   The charset used in Content-Type header. UTF-8, if not specified.

How can you be sure that the output produced by git log etc. that are used in the script are in the encoding specified by this variable? IOW, wouldn't log.outputencoding be the better choice to use in the Content-Type header?

-- Hannes
Previous: Alexey ShumkinNext: Shumkin Alexey
Message 3 of 12 in “post-receive-email: explicitly set Content-Type header”
  1. post-receive-email: explicitly set Content-Type headerAlexey Shumkin, Sep 20, 2011
  2. post-receive-email: explicitly set Content-Type headerAlexey Shumkin, Sep 20, 2011
  3. Johannes SixtSep 20, 2011
  4. Shumkin AlexeySep 20, 2011
  5. Johannes SixtSep 20, 2011
  6. Jonathan NiederOct 7, 2011
  7. Alexey ShumkinOct 7, 2011
  8. Jonathan NiederOct 7, 2011
  9. post-receive-email: explicitly set Content-Type headerAlexey Shumkin, Nov 9, 2011
  10. Junio C HamanoNov 9, 2011
  11. Alexey ShumkinNov 9, 2011
  12. Jakub NarebskiSep 20, 2011

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.