From: Mark Wielaard <mark@klomp.org>
To: Benson Muite <benson_muite@emailplus.org>
Cc: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
newlib@sourceware.org, gdb-patches@sourceware.org,
elfutils-devel@sourceware.org, libabigail@sourceware.org,
binutils@sourceware.org
Subject: Re: Updating mailman settings to avoid From rewriting
Date: Sun, 8 Oct 2023 23:12:11 +0200 [thread overview]
Message-ID: <20231008211211.GH728@gnu.wildebeest.org> (raw)
In-Reply-To: <66ed5bf6-a39e-b29a-e683-c1da564e7be5@emailplus.org>
Hi,
On Sat, Oct 07, 2023 at 03:20:55PM +0300, Benson Muite wrote:
> On 10/7/23 06:55, Thiago Jung Bauermann wrote:
> > Mark Wielaard <mark@klomp.org> writes:
> >>> Also the newlib and gdb-patches mailinglists don't have an admin at
> >>> the moment. Could someone volunteer to act as list admin for these?
> >>
> >> We still need admins/moderators for these two lists.
> >
> > I'm not a maintainer or anything in GDB nor GNU, but if that isn't a
> > prerequisite and if other people are OK with it I'd be happy to be list
> > admin for gdb-patches.
> >
> Would be happy to help with newlib
That would be nice. Note that it can be a shared responsibility. And
it isn't really much work. Two or three times a month there is spam
(most is filtered out before it hits the list) or a message that is
too big gets caught in moderation. And you can block people from
posting to the list in an emergency (or when gdb or newlib has a code
of conduct committee, when they decide to give someone a
timeout). Although that last one luckily only happens once every
couple of years.
If none of the gdb or newlib maintainers objects I can add you and
sent you the list password. Please sent me your PGP key if you have
one so I can sent you the authentication details in private.
Cheers,
Mark
next prev parent reply other threads:[~2023-10-08 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 22:12 Mark Wielaard
2023-10-07 0:14 ` Mark Wielaard
2023-10-07 3:55 ` Thiago Jung Bauermann
2023-10-07 12:20 ` Benson Muite
2023-10-08 21:12 ` Mark Wielaard [this message]
2023-10-14 1:14 ` 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=20231008211211.GH728@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=benson_muite@emailplus.org \
--cc=binutils@sourceware.org \
--cc=elfutils-devel@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=libabigail@sourceware.org \
--cc=newlib@sourceware.org \
--cc=thiago.bauermann@linaro.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).