From: Fabian Emmes <emmes@informatik.rwth-aachen.de>
To: git@vger.kernel.org
Subject: Re: [PATCH] post-receive-email: Set content-type and encoding in generated mail
Date: Thu, 30 Jul 2009 10:02:06 +0200 [thread overview]
Message-ID: <20090730080206.GR31428@hebe.informatik.RWTH-Aachen.DE> (raw)
In-Reply-To: <20090729144610.GA5060@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
Hi,
thanks Teemu and Jeff for correcting the errors. Indeed I assumed that
git log would always output UTF-8 and a "Content-Type" header would be
valid on its own. The patch of Jeff solves my problem. I tested the
results in mutt, kmail and thunderbird.
Regards,
Fabian
On 29. Jul, 10:46, Jeff King wrote:
> On Wed, Jul 29, 2009 at 03:48:24PM +0200, Fabian Emmes wrote:
>
> > --- 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
>
> Shouldn't this be $(git config i18n.logOutputEncoding), since you will
> be inserting the output of git rev-list into the mail?
>
> And as Teemu mentioned, you need a mime-version and a transfer-encoding
> header, as well.
>
> So maybe (totally untested):
>
> ---
> diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
> index 2a66063..0c1c6ad 100755
> --- a/contrib/hooks/post-receive-email
> +++ b/contrib/hooks/post-receive-email
> @@ -192,11 +192,16 @@ generate_email()
>
> generate_email_header()
> {
> + encoding=`git config i18n.logOutputEncoding`
> + test -z "$encoding" && encoding=utf-8
> # --- Email (all stdout will be the email)
> # Generate header
> cat <<-EOF
> To: $recipients
> Subject: ${emailprefix}$projectdesc $refname_type, $short_refname, ${change_type}d. $describe
> + MIME-Version: 1.0
> + Content-Type: text/plain; charset=$encoding
> + Content-Transfer-Encoding: 8bit
> X-Git-Refname: $refname
> X-Git-Reftype: $refname_type
> X-Git-Oldrev: $oldrev
--
Fabian Emmes mailto:emmes@informatik.rwth-aachen.de
LuFG Informatik 2 http://verify.rwth-aachen.de/emmes/
RWTH Aachen phone: +49 241 80-21241
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-07-30 8:02 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
2009-07-29 14:46 ` Jeff King
2009-07-30 8:02 ` Fabian Emmes [this message]
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=20090730080206.GR31428@hebe.informatik.RWTH-Aachen.DE \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).