Re: Is git am supposed to decode MIME?
- From
Jeff King <peff@peff.net>
- Date
- Oct 4, 2017, 09:25 UTC
- Message-ID
- <20171004092546.vnjddxqwvia5cfn6@sigill.intra.peff.net>
- In-Reply-To
- <24940e12-3f72-1ef0-0983-58523d8dec51@redhat.com>
On Wed, Oct 04, 2017 at 10:44:31AM +0200, Florian Weimer wrote:
Show 8 quoted lines
> The git am documentation talks about “mailboxes”. I suppose these contain > messages in Internet Mail syntax. Is git am supposed to decode MIME? > > I'm asking because I have a message whose body is encoded as > quoted-printable, but git am does not parse the patch contained in it. > > If git am is supposed to deal with this, I'll dig deeper and try to figure > out where things go wrong.
Yes, it should. I just double-checked with the toy patch patch below, and it correctly extracted the quoted-printable from the commit message and patch, as well as in the headers.
-- >8 -- From peff@peff.net Wed Oct 4 05:21:57 2017 Date: Wed, 4 Oct 2017 05:21:55 -0400 From: =?utf-8?Q?=C3=81ccented N=C3=A1me?= <peff@peff.net> To: Jeff King <peff@peff.net> Subject: [PATCH] add 8bit content MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
This commit message also has s=C3=B3me 8-bit characters which will need qp-encoding.
Signed-off-by: =C3=81ccented N=C3=A1me <peff@peff.net> --- file | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/file b/file index d95f3ad..d39c7fc 100644 --- a/file +++ b/file @@ -1 +1 @@ -content +8-bit c=C3=B3ntent --=20 2.14.2.1117.g65a3442612