All of lore.kernel.org
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: Fabian Emmes <emmes@informatik.rwth-aachen.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] post-receive-email: Set content-type and encoding in generated mail
Date: Wed, 29 Jul 2009 17:00:39 +0300	[thread overview]
Message-ID: <87tz0vwpvc.fsf@iki.fi> (raw)
In-Reply-To: <1248875304-13167-1-git-send-email-emmes@informatik.rwth-aachen.de> (Fabian Emmes's message of "Wed, 29 Jul 2009 15:48:24 +0200")

On 2009-07-29 15:48 (+0200), Fabian Emmes wrote:

> 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

That's not complete. You need all these:

    MIME-Version: 1.0
    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: 8bit

  reply	other threads:[~2009-07-29 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 13:48 [PATCH] post-receive-email: Set content-type and encoding in generated mail Fabian Emmes
2009-07-29 14:00 ` Teemu Likonen [this message]
2009-07-29 14:46 ` Jeff King
2009-07-30  8:02   ` Fabian Emmes
2009-07-31  1:52     ` Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2009-07-29  9:43 Fabian Emmes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tz0vwpvc.fsf@iki.fi \
    --to=tlikonen@iki.fi \
    --cc=emmes@informatik.rwth-aachen.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.