From: Mark Wielaard <mark@klomp.org>
To: Aldy Hernandez via Overseers <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, Aldy Hernandez <aldyh@redhat.com>
Subject: Re: A non-text attachment was scrubbed...
Date: Sat, 17 Sep 2022 11:31:33 +0200 [thread overview]
Message-ID: <20220917093133.GF29694@gnu.wildebeest.org> (raw)
In-Reply-To: <CAGm3qMXUU7cS23f1878JZinKXEndX1hA1OWUMCvfT9LZuKSkOA@mail.gmail.com>
Hi Aldy,
On Fri, Sep 16, 2022 at 03:29:32PM +0200, Aldy Hernandez via Overseers wrote:
> My latest post to gcc-patches:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601696.html
>
> ...says:
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 0001-Rewrite-NAN-and-sign-handling-in-frange.patch
> Type: text/x-patch
> Size: 49883 bytes
> Desc: not available
> URL: <https://gcc.gnu.org/pipermail/gcc-patches/attachments/20220916/1d3742fe/attachment-0001.bin>
>
> But isn't this a text attachment? I mean, it says text/x-patch right there.
I haven't found the mailman setting that caused this yet. But I
expect it only regards simple text/plain to be real text-only
attachements.
Note that the public-inbox archive does display the text/x-patch
attachements "inline":
https://inbox.sourceware.org/gcc-patches/CAGm3qMXtoe4N1nh=Td4sUMX2xA=7Y2i4HT+2QjrSuf=j1yXE+w@mail.gmail.com/T/
Cheers,
Mark
prev parent reply other threads:[~2022-09-17 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 13:29 Aldy Hernandez
2022-09-17 9:31 ` Mark Wielaard [this message]
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=20220917093133.GF29694@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=aldyh@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.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).