From: Jon Jensen <jon@endpoint.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, Gerrit Pape <pape@smarden.org>,
Alexey Shumkin <zapped@mail.ru>, Johannes Sixt <j6t@kdbg.org>,
Michael Haggerty <mhagger@alum.mit.edu>
Subject: Re: [PATCH/RFC 0/2] post-receive-email: declaring and consistently using one output encoding
Date: Wed, 14 Mar 2012 11:54:50 -0600 (MDT) [thread overview]
Message-ID: <alpine.LFD.2.02.1203141153460.4355@fnzzl> (raw)
In-Reply-To: <7v62eeewl8.fsf@alter.siamese.dyndns.org>
On Thu, 8 Mar 2012, Junio C Hamano wrote:
>> Patches are targetted at 1.7.11 unless there is overwhelming interest
>> in them landing sooner.
>
> Even if there is none, I wouldn't mind taking it for 1.7.10, if only to
> reduce the chance that the patch gets forgotten again, provided that
> there is a clear concensus that this is a good change that won't regress
> people who have been actually using this sample in real life.
+1 from me. This would solve an occasional problem we have because
encodings aren't set in post-receive-email output.
Jon
prev parent reply other threads:[~2012-03-14 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 11:51 [PATCH/RFC 0/2] post-receive-email: declaring and consistently using one output encoding Jonathan Nieder
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 [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.02.1203141153460.4355@fnzzl \
--to=jon@endpoint.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jrnieder@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).