From: Andre Przywara <andre.przywara@amd.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Andre Przywara <andre.przywara@amd.com>
Subject: Re: [PATCH] allow 8bit data in email body sent by send-email
Date: Fri, 9 Jan 2009 15:16:24 +0100 [thread overview]
Message-ID: <49675C38.8060208@amd.com> (raw)
In-Reply-To: <20090109072814.GA21180@coredump.intra.peff.net>
Jeff King wrote:
>> when sending patch files via git send-email, the perl script assumes
>> 7bit characters only. If there are other bytes in the body (foreign language
>> characters in names or translations), some servers (like vger.kernel.org)
>> reject the mail because of th?t. This patch always adds an 8bit header line
>> to each mail.
>
> This should be done already by git-format-patch when you generate the
> patch to feed to send-email.
Well, this could be discussed, after all the problem lies in the actual
transportation, which should be the responsibility of git-send-email.
But I am OK with putting this into format-patch.
> What exactly is the workflow you use to generate this problem?
I use git format-patch to generate a patch file for a single-mail patch
(not a patch series). Then I edit this file manually to add questions
and comments and include my signature. During this step the umlauts came
in. If you have a suggestion to improve this workflow, I am all ears, I
am fairly new to git.
> Does it matter where the non-ascii characters are
> (commit versus patch, etc)?
Oh, right you are. If there are 8bit characters in the commit message,
git-format-patch adds the appropriate headers.
> What version of git are you using?
Version 1.5.5 on one machine and 1.5.2.2 on another. I know, i know ;-)
but I haven't had time to compile a newer one, yet.
>
>> diff --git a/git-send-email.perl b/git-send-email.perl
>> index 77ca8fe..68a462c 100755
>> --- a/git-send-email.perl
>> +++ b/git-send-email.perl
>> @@ -793,6 +793,7 @@ To: $to${ccline}
>> Subject: $subject
>> Date: $date
>> Message-Id: $message_id
>> +Content-Transfer-Encoding: 8bit
>> X-Mailer: git-send-email $gitversion
>> ";
>
> This fix isn't right anyway. For one thing, if you're going to include
> C-T-E, you should also include a MIME-Version header. But more
> importantly, we are already handling encoding elsewhere. So
> unconditionally adding this means that you may conflict with existing
> MIME headers in the @xh variable.
Ok, so what about adding a flag to git-format-patch that forces the 8bit
headers on? I think a workaround would be to add a --subject-prefix with
a special character and later remove this, but this is not really a
long-term solution ;-)
Thanks and regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Jochen Polster; Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2009-01-09 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 13:50 [PATCH] allow 8bit data in email body sent by send-email Andre Przywara
2009-01-09 7:28 ` Jeff King
2009-01-09 14:16 ` Andre Przywara [this message]
2009-01-09 14:44 ` Jeff King
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=49675C38.8060208@amd.com \
--to=andre.przywara@amd.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).