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

[PATCH/RFC 0/3] post-receive-email: explicitly set Content-Type header

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 2, 2013, 23:21 UTC
Message-ID
<20130802232118.GB2963@elie.Belkin>
Hi all,

This is a revival of [1], which declares encoding in emails to make it more likely that they can be read. I like to think it avoids the mistakes of previous attempts, but I'll let you judge. :)

Sorry for the long delay.  Thoughts of all kinds welcome, as always.

Thanks, Jonathan

Gerrit Pape (1):
  hooks/post-receive-email: set declared encoding to utf-8
Jonathan Nieder (2):
  hooks/post-receive-email: use plumbing instead of 'git log' and 'git show'
  hooks/post-receive-email: force log messages in UTF-8
 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=183070
Next: Jonathan Nieder
Message 1 of 7 in “post-receive-email: explicitly set Content-Type header”
  1. 0/3 post-receive-email: explicitly set Content-Type headerJonathan Nieder, Aug 2, 2013
  2. 1/3 hooks/post-receive-email: use plumbing instead of git log/showJonathan Nieder, Aug 2, 2013
  3. 2/3 hooks/post-receive-email: force log messages in UTF-8Jonathan Nieder, Aug 2, 2013
  4. Alexey ShumkinAug 4, 2013
  5. Jonathan NiederAug 4, 2013
  6. Alexey ShumkinAug 5, 2013
  7. 3/3 hooks/post-receive-email: set declared encoding to utf-8Jonathan Nieder, Aug 2, 2013

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.