From: Chris Faylor <postmaster@sourceware.org>
To: W Brown <webrown.cpp@gmail.com>
Cc: overseers@sourceware.org
Subject: Re: Fwd: Libstdc++ Digest, Vol 9, Issue 48
Date: Wed, 18 Nov 2020 23:57:14 -0500 [thread overview]
Message-ID: <20201119045324.GA15067@cgf.cx> (raw)
In-Reply-To: <64EA3630-E31F-45A2-8855-601E7C2ADC67@gmail.com>
[Redirecting to postmaster. PLEASE use the postmaster account for email
issues]
On Wed, Nov 18, 2020 at 03:30:18PM -0600, W Brown wrote:
>Here's another example of a messed-up Digest message.
I'm subscribed to the libstdc++ digest at a gmail account and don't see
any problems with the digest I received. The patch attachments came
through fine.
Since we have 92 people reading the digest and you are the only one
complaining it's possible that the issue is with whatever you're using
to read email.
>> 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--
>>
>>
>
>
prev parent reply other threads:[~2020-11-19 4:57 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
2020-11-19 4:57 ` Chris Faylor [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=20201119045324.GA15067@cgf.cx \
--to=postmaster@sourceware.org \
--cc=overseers@sourceware.org \
--cc=webrown.cpp@gmail.com \
/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).