Junio C Hamano wrote:
> By convention, the commit message and the author/committer names
> in the commit objects are UTF-8 encoded. When formatting for
> e-mails, Q-encode them according to RFC 2047.
>
> While we are at it, generate the content-type and
> content-transfer-encoding headers as well.
>
> Signed-off-by: Junio C Hamano <junkio@xxxxxxx>
>
> ---
>
> With this patch, the output formatted with
>
> git show --pretty=email --patch-with-stat 9d7f73d4
>
> would start like this:
>
> From 9d7f73d43fa49d0d2f5a8cfcce9d659e8ad2d265 Thu Apr 7 15:13:13 2005
> From: =?utf-8?q?Lukas_Sandstr=C3=B6m?= <lukass@xxxxxxxxxxxxxxxx>
> Date: Sat, 25 Feb 2006 12:20:13 +0100
> Subject: [PATCH] git-fetch: print the new and old ref when fast-forwarding
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
I guess that we also need
MIME-Version: 1.0
(from what I remember of troubles with Eoutlook Express not sending all
the required headers, and tin not working properly).
If I remember correctly encoding headers using quoted-printable is needed
only because headers are before charset is set. IIRC there was proposal
to use UTF-8 for headers regardless of the charset used for body of message.
P.S. Should we set User-Agent header as well?
--
Jakub Narebski
Warsaw, Poland
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html