MBOX-Line: From blong at google.com  Wed Dec  3 14:10:35 2014
To: imap-protocol@u.washington.edu
From: Brandon Long <blong@google.com>
Date: Fri Jun  8 12:34:53 2018
Subject: [Imap-protocol] GMail and Content-Type: text/x-patch,
 Content-Disposition: inline; filename=blah.patch
In-Reply-To: <74f73395-7fb8-4809-ba03-9209bb653322@flaska.net>
References: <74f73395-7fb8-4809-ba03-9209bb653322@flaska.net>
Message-ID: <CABa8R6udVLch=-LfD1XTE-TejoMwvq=+1x4NTkdvwAY5xfEnDA@mail.gmail.com>

This seems way out of IMAP territory, but I've filed a bug for the frontend
team to look at it.

Brandon

On Tue, Nov 25, 2014 at 2:31 AM, Jan Kundr?t <jkt@flaska.net> wrote:

> Hi Brandon,
> I was talking with Gerrit's developers about how to improve the e-mails
> they generate (Gerrit is a patch review system tightly integrated with
> Git). They told me that GMail's web interface doesn't show the patch
> inline, as requested. Here's how the generated e-mail looks like:
>
> * Content-Type: multipart/mixed
> |
> +--* Content-Type: text/plain; charset=utf-8; format=flowed
> |    (the textual description)
> |
> +--* Content-Type: text/x-patch
>     Content-Disposition: inline; filename=0001-blah-blah.patch
>     Content-Transfer-Encoding: base64
>     (the patch goes here)
>
> What I was hoping to achieve was a display of both parts in sequence, as
> if the e-mail was embedded into the main textual body part. What I got back
> instead is the rendering shown in the attached image.
>
> Is there something I could do to let GMail render the patch as-is, without
> extra clicking, while at the same time making it possible to open the patch
> in an external viewer by other clients?
>
> With kind regards,
> Jan
>
> --
> Trojit?, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20141203/bddf961e/attachment.html>
