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

Jonathan Nieder [off-list ref] 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.

[off-list ref] 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

On Thu, 8 Mar 2012, Junio C Hamano wrote:

quoted

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