From: Thomas Schwinge <thomas@schwinge.name>
To: overseers@sourceware.org
Cc: thomas.schwinge@siemens.com
Subject: GCC email not getting through
Date: Mon, 05 Jun 2023 16:33:20 +0200 [thread overview]
Message-ID: <87r0qqx9lb.fsf@euler.schwinge.homeip.net> (raw)
Hi!
I'm subscribed to a good number of GCC/Sourceware mailing lists via
<thomas@schwinge.name>. As far as I can tell, I've had my last GCC email
delivered more than 10 hours ago: "Date: Sun, 04 Jun 2023 22:59:16 -0500"
(that is, 05:59 CEST). That's... ;-) unusual. In other words, I do see
emails on <https://inbox.sourceware.org/gcc/>,
<https://inbox.sourceware.org/gcc-patches/>, etc. that I do not have in
my mailbox. A lot of other emails (from different sites) I've received
all day; so far found nothing missing but GCC mailing lists.
For example, per
<https://gcc.gnu.org/mailman/options/gcc/thomas%40schwinge.name>,
<https://gcc.gnu.org/mailman/options/gcc-patches/thomas%40schwinge.name>,
I'm subscribed and "Mail delivery": "Enabled".
Will you please check if there's anything wrong/queued/bounced/etc. for
<thomas@schwinge.name> on your side?
Grüße
Thomas
next reply other threads:[~2023-06-05 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 14:33 Thomas Schwinge [this message]
2023-06-05 14:36 ` Frank Ch. Eigler
2023-06-05 21:38 ` Resolved: " Mark Wielaard
2023-06-14 21:52 ` Mark Wielaard
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=87r0qqx9lb.fsf@euler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=overseers@sourceware.org \
--cc=thomas.schwinge@siemens.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).