From: Tobias Burnus <tobias@codesourcery.com>
To: <overseers@gcc.gnu.org>
Subject: GCC email archive – text/x-patch attachments
Date: Wed, 22 Jul 2020 08:23:00 +0200 [thread overview]
Message-ID: <53689161-7c14-bfa6-3667-0c356b5fddaf@codesourcery.com> (raw)
Hi,
while "text/plain" attachments show up as text,
"text/x-patch" emails show up as "A non-text attachment was scrubbed..."
and clicking on the attachment offers a file without content-type and
suffix .bin – hence browsers do not show the attachment but just offer to
download it.
Example: https://gcc.gnu.org/pipermail/gcc-patches/2020-July/550154.html
Is there the chance to handle all text/* and in particular text/x-patch
similar to text/plain?
Thanks,
Tobias
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
reply other threads:[~2020-07-22 6:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53689161-7c14-bfa6-3667-0c356b5fddaf@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=overseers@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).