public inbox for
 help / color / mirror / Atom feed
From: W Brown <>
Subject: Fwd: Libstdc++ Digest, Vol 9, Issue 47
Date: Wed, 18 Nov 2020 09:58:37 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Here's another example of a Digest that's borked.  I'll keep sending such examples from time to time until you have enough information to sort out the cause.

Thanks.  Best,

-- WEB

> Begin forwarded message:
> From:
> Subject: Libstdc++ Digest, Vol 9, Issue 47
> Date: 2020-11-18 at 6:00:03 AM CST
> To:
> Reply-To:
> --iDgFKLa5Kp4Ejml3
> 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: 6964
> --iDgFKLa5Kp4Ejml3--

           reply	other threads:[~2020-11-18 15:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).