From: W Brown <webrown.cpp@gmail.com>
To: overseers@gcc.gnu.org
Subject: Fwd: Libstdc++ Digest, Vol 9, Issue 48
Date: Wed, 18 Nov 2020 15:30:18 -0600 [thread overview]
Message-ID: <64EA3630-E31F-45A2-8855-601E7C2ADC67@gmail.com> (raw)
In-Reply-To: <mailman.222317.1605732609.8982.libstdc++@gcc.gnu.org>
Here's another example of a messed-up Digest message.
> Begin forwarded message:
>
> From: libstdc++-request@gcc.gnu.org
> Subject: Libstdc++ Digest, Vol 9, Issue 48
> Date: 2020-11-18 at 2:50:09 PM CST
> To: libstdc++@gcc.gnu.org
> Reply-To: libstdc++@gcc.gnu.org
>
>
>
>
> --iRomnA/8S0UoJbe2
> Content-Transfer-Encoding: 7BIT
> Content-Disposition: ATTACHMENT;
> filename=patch.txt
> Content-Type: TEXT/X-PATCH;
> charset=us-ascii;
> name="patch.txt"
> X-Apple-Content-Length: 2971
>
>
> --iRomnA/8S0UoJbe2--
>
>
>
>
>
> --cNdxnHkX5QqsyA0e
> Content-Transfer-Encoding: 7BIT
> Content-Disposition: ATTACHMENT;
> filename=patch.txt
> Content-Type: TEXT/PLAIN;
> charset=us-ascii;
> name="patch.txt"
> X-Apple-Content-Length: 2814
>
>
> --cNdxnHkX5QqsyA0e--
>
>
next parent reply other threads:[~2020-11-18 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.222317.1605732609.8982.libstdc++@gcc.gnu.org>
2020-11-18 21:30 ` W Brown [this message]
2020-11-19 4:57 ` Chris Faylor
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=64EA3630-E31F-45A2-8855-601E7C2ADC67@gmail.com \
--to=webrown.cpp@gmail.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).