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

[PATCH/RFC 0/2] post-receive-email: declaring and consistently using one output encoding

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Mar 8, 2012, 11:51 UTC
Message-ID
<20120308115119.GA2604@burratino>
Hi,

These patches revisit the bug described at [1], where the sample post-receive script annoys receiving MUAs by not declaring what encoding it uses. Worse, sometimes the mails have a mixture of encodings.

These patches standardize on UTF-8, but that is only for the sake of simplicity. A patch on top to make the choice of encoding customizable would probably not be too complicated, if someone is interested.

Patches are targetted at 1.7.11 unless there is overwhelming interest in them landing sooner. Thanks to Alexander Gerasiov <gq@cs.msu.su> for the writing a patch long ago to get this started[1].

Thoughts?
Gerrit Pape (1):
  bug#506445: hooks/post-receive-email: set encoding to utf-8
Jonathan Nieder (1):
  post-receive-email: defend against non-utf8 [i18n] logoutputencoding
    setting
 contrib/hooks/post-receive-email |   15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

[1] http://thread.gmane.org/gmane.comp.version-control.git/181737/focus=181755 [2] http://bugs.debian.org/506445

Next: Jonathan Nieder
Message 1 of 9 in “post-receive-email: declaring and consistently using one output encoding”
  1. 0/2 post-receive-email: declaring and consistently using one output encodingJonathan Nieder, Mar 8, 2012
  2. 1/2 hooks/post-receive-email: set encoding to utf-8Jonathan Nieder, Mar 8, 2012
  3. 2/2 post-receive-email: defend against non UTF-8 i18n.logoutputencoding settingJonathan Nieder, Mar 8, 2012
  4. Jeff KingMar 8, 2012
  5. Jonathan NiederMar 8, 2012
  6. Alexey ShumkinMar 14, 2012
  7. Jonathan NiederMar 14, 2012
  8. Junio C HamanoMar 8, 2012
  9. Jon JensenMar 14, 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.