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

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 8, 2012, 19:12 UTC
Message-ID: <7v62eeewl8.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20120308115119.GA2604@burratino>

Jonathan Nieder <jrnieder@gmail.com> writes:

> 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.

Show 17 quoted lines

> <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