git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Jon Jensen <jon@endpoint.com>
Date
Mar 14, 2012, 17:54 UTC
Message-ID
<alpine.LFD.2.02.1203141153460.4355@fnzzl>
In-Reply-To
<7v62eeewl8.fsf@alter.siamese.dyndns.org>
On Thu, 8 Mar 2012, Junio C Hamano wrote:
Show 7 quoted lines
>> 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
Previous: Junio C Hamano
Message 9 of 9 in “post-receive-email: declaring and consistently using one output encoding”
  1. 0/2 post-receive-email: declaring and consistently using one output encodingJonathan Nieder, Mar 8, 2012
  2. 1/2 hooks/post-receive-email: set encoding to utf-8Jonathan Nieder, Mar 8, 2012
  3. 2/2 post-receive-email: defend against non UTF-8 i18n.logoutputencoding settingJonathan Nieder, Mar 8, 2012
  4. Jeff KingMar 8, 2012
  5. Jonathan NiederMar 8, 2012
  6. Alexey ShumkinMar 14, 2012
  7. Jonathan NiederMar 14, 2012
  8. Junio C HamanoMar 8, 2012
  9. Jon JensenMar 14, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.