From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Cc: Gerrit Pape <pape@smarden.org>, Alexey Shumkin <zapped@mail.ru>,
Johannes Sixt <j6t@kdbg.org>,
Michael Haggerty <mhagger@alum.mit.edu>,
Jon Jensen <jon@endpoint.com>
Subject: [PATCH/RFC 0/2] post-receive-email: declaring and consistently using one output encoding
Date: Thu, 8 Mar 2012 05:51:19 -0600 [thread overview]
Message-ID: <20120308115119.GA2604@burratino> (raw)
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 reply other threads:[~2012-03-08 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 11:51 Jonathan Nieder [this message]
2012-03-08 11:57 ` [PATCH 1/2] hooks/post-receive-email: set encoding to utf-8 Jonathan Nieder
2012-03-08 11:59 ` [PATCH 2/2] post-receive-email: defend against non UTF-8 i18n.logoutputencoding setting Jonathan Nieder
2012-03-08 13:50 ` Jeff King
2012-03-08 13:52 ` Jonathan Nieder
2012-03-14 19:36 ` Alexey Shumkin
2012-03-14 19:55 ` Jonathan Nieder
2012-03-08 19:12 ` [PATCH/RFC 0/2] post-receive-email: declaring and consistently using one output encoding Junio C Hamano
2012-03-14 17:54 ` Jon Jensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120308115119.GA2604@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=jon@endpoint.com \
--cc=mhagger@alum.mit.edu \
--cc=pape@smarden.org \
--cc=zapped@mail.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).