From: Carlos O'Donell <carlos@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Subject: glibc ML access and moderation?
Date: Thu, 2 Apr 2020 22:55:05 -0400 [thread overview]
Message-ID: <90a019fe-506e-31f5-942f-6559f9cc4cf8@redhat.com> (raw)
May I please get all of the credentials for glibc lists?
It looks like some things are going into the moderation
queue and I should be handling that for the community.
I need credentials for:
libc-alpha
libc-help
libc-locales
libc-ports
libc-stable
libc-testresults
glibc-cvs
glibc-bugs
I already have access to libc-announce.
Thank you!
--
Cheers,
Carlos.
next reply other threads:[~2020-04-03 2:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 2:55 Carlos O'Donell [this message]
2020-04-03 3:09 ` 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=90a019fe-506e-31f5-942f-6559f9cc4cf8@redhat.com \
--to=carlos@redhat.com \
--cc=overseers@sourceware.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).