From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@gcc.gnu.org
Subject: 29 Gcc-announce moderator request(s) waiting (fwd)
Date: Sat, 21 Mar 2020 09:17:21 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.2003210914310.4184@anthias.pfeifer.com> (raw)
I have been getting this daily for a week now, but do not have a
password.
http://gcc.gnu.org/mailman/admindb/gcc-announce says
Gcc-announce list run by gcc-announce-owner at gcc.gnu.org
Who is behind gcc-announce-owner? And could they/we please get
a password?
And is there a way to expire requests after 48 hours? That would
be quite convenient.
Thank you,
Gerald
---------- Forwarded message ----------
From: gcc-announce-bounces@gcc.gnu.org
To: gcc-announce-owner@gcc.gnu.org
Date: Sat, 21 Mar 2020 08:00:02 +0000
Subject: 29 Gcc-announce moderator request(s) waiting
The Gcc-announce@gcc.gnu.org mailing list has 29 request(s) waiting
for your consideration at:
http://gcc.gnu.org/mailman/admindb/gcc-announce
Please attend to this at your earliest convenience. This notice of
pending requests, if any, will be sent out daily.
Pending posts:
From: ext-ticket@google.com on Thu Mar 12 14:29:36 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 14:36:57 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 14:43:26 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:02:34 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:21:21 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:25:27 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:31:59 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:32:00 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:33:38 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:34:41 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: julyighor@gmail.com on Thu Mar 12 15:38:29 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post to moderated list
From: ext-ticket@google.com on Thu Mar 12 15:39:44 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:39:48 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:47:10 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 15:55:37 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 16:04:57 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 16:06:23 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: carlos.roquette@globo.com on Thu Mar 12 16:08:18 2020
Subject: RES: t/45357122 GCC 9.3 Released
Cause: Post to moderated list
From: ext-ticket@google.com on Thu Mar 12 16:09:00 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: cppadict@globo.com on Thu Mar 12 16:10:06 2020
Subject: RES: t/45357122 GCC 9.3 Released
Cause: Post to moderated list
From: ext-ticket@google.com on Thu Mar 12 16:11:25 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: ext-ticket@google.com on Thu Mar 12 16:12:50 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: pushpenders@redbytes.in on Thu Mar 12 16:25:17 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post to moderated list
From: ext-ticket@google.com on Thu Mar 12 19:19:15 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post by non-member to a members-only list
From: fcqqfat@163.com on Fri Mar 13 00:29:53 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post to moderated list
From: fcqqfat@163.com on Fri Mar 13 00:30:30 2020
Subject: Re: t/45357122 GCC 9.3 Released
Cause: Post to moderated list
From: divyajitdarbar@gmail.com on Fri Mar 13 01:07:36 2020
Subject: Unsubscribe to Emails
Cause: Post to moderated list
From: girveer17vollaymarketing@gmail.com on Mon Mar 16 19:25:54 2020
Subject: RE: PAYMENT SWIFT COPY FOR = USD 80,950.25
Cause: Post by non-member to a members-only list
From: orders@msc.com on Wed Mar 18 09:15:01 2020
Subject: Re: March Order
Cause: Post by non-member to a members-only list
next reply other threads:[~2020-03-21 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 8:17 Gerald Pfeifer [this message]
2020-03-21 15:08 ` Gerald Pfeifer
2020-03-21 15:16 ` Fixing up list archives? (was: 29 Gcc-announce moderator request(s) waiting) Gerald Pfeifer
2020-03-22 5:44 ` 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.2003210914310.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).