| commit | 53a7296e7ebab82d23983fd5506a2bf5ee5d2d0c | |
| author | Gerrit Pape <pape@smarden.org> | |
| Thu, 11 Dec 2008 20:27:21 +0000 (11 20:27 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 5 Aug 2013 17:17:38 +0000 (5 10:17 -0700) | ||
| tree | fe0960f6ab0f8a16d5179b346e5335de72c7c733 | treesnapshot (tar.gz zip) |
| parent | 3109bdb0d157afbd01c412d6f3fb1c86d8b7adde | commitdiff |
hooks/post-receive-email: set declared encoding to utf-8
Some email clients (e.g., claws-mail) display the message body
incorrectly when the charset is not defined explicitly in a
Content-Type header. "git log" generates logs in UTF-8 encoding by
default, so add a Content-Type header declaring that encoding to
the emails the post-receive-email example hook sends.
[jn: also setting the Content-Transfer-Encoding so MTAs know what
kind of mangling might be needed when sending to a non 8-bit clean
SMTP host]
Requested-by: Alexander Gerasiov <gq@debian.org>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Some email clients (e.g., claws-mail) display the message body
incorrectly when the charset is not defined explicitly in a
Content-Type header. "git log" generates logs in UTF-8 encoding by
default, so add a Content-Type header declaring that encoding to
the emails the post-receive-email example hook sends.
[jn: also setting the Content-Transfer-Encoding so MTAs know what
kind of mangling might be needed when sending to a non 8-bit clean
SMTP host]
Requested-by: Alexander Gerasiov <gq@debian.org>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| contrib/hooks/post-receive-email | diffblobblamehistory |