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

[PATCH] post-receive-email: Set content-type and encoding in generated mail

From
FEFabian Emmes <emmes@informatik.rwth-aachen.de>
Date
Jul 29, 2009, 09:43 UTC
Message-ID
<1248860622-11814-1-git-send-email-emmes@informatik.rwth-aachen.de>

Add proper content-type header to mails generated by post-receive-email, as suggested by Alexander Gerasiov in http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg588535.html

Signed-off-by: Fabian Emmes <emmes@informatik.rwth-aachen.de>
---
 contrib/hooks/post-receive-email |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
index 2a66063..0c50155 100755
--- a/contrib/hooks/post-receive-email
+++ b/contrib/hooks/post-receive-email
@@ -197,6 +197,7 @@ generate_email_header()
 	cat <<-EOF
 	To: $recipients
 	Subject: ${emailprefix}$projectdesc $refname_type, $short_refname, ${change_type}d. $describe
+	Content-Type: text/plain; charset=utf-8
 	X-Git-Refname: $refname
 	X-Git-Reftype: $refname_type
 	X-Git-Oldrev: $oldrev
-- 
1.6.3.1.9.g95405b
Message 1 of 1 in “post-receive-email: Set content-type and encoding in generated mail”
  1. post-receive-email: Set content-type and encoding in generated mailFabian Emmes, Jul 29, 2009

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.