From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@gcc.gnu.org
Subject: Fixing up list archives? (was: 29 Gcc-announce moderator request(s) waiting)
Date: Sat, 21 Mar 2020 16:16:05 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.2003211609030.4184@anthias.pfeifer.com> (raw)
In-Reply-To: <alpine.LSU.2.21.2003210914310.4184@anthias.pfeifer.com>
I noticed something (maybe someone) has allowed a number of bogus
mails to get through into the archive, cf.
https://gcc.gnu.org/pipermail/gcc-announce/2020/thread.html
Is there a way to take these out again?
Gerald
PS: I have unsubscribed admin@txcorp.com and it@txcorp.com, whose
ticket system appears to have created a bit of a mess.
next prev parent reply other threads:[~2020-03-21 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 8:17 29 Gcc-announce moderator request(s) waiting (fwd) Gerald Pfeifer
2020-03-21 15:08 ` Gerald Pfeifer
2020-03-21 15:16 ` Gerald Pfeifer [this message]
2020-03-22 5:44 ` Fixing up list archives? (was: 29 Gcc-announce moderator request(s) waiting) Christopher Faylor
2020-03-22 5:47 ` Christopher 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=alpine.LSU.2.21.2003211609030.4184@anthias.pfeifer.com \
--to=gerald@pfeifer.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).