From: Angela Marie Thomas <angela@foam.wonderslug.com>
To: overseers@sources.redhat.com
Subject: removing someone from the global deny list
Date: Tue, 02 Mar 2004 02:48:00 -0000 [thread overview]
Message-ID: <20040302025912.27BE7E3A67@foam.wonderslug.com> (raw)
One of Geoff's colleagues, zlaski@apple.com, somehow ended up on the
global deny list. Can someone please remove him and, if possible,
tell me how he got on it so he doesn't end up on it again? I'm not
wise in the ways of qmail/ezmlm so I'm not really sure what he did
to get on the deny list.
His bounce message said to contact gcc-patches-owner@gcc.gnu.org.
Can that person remove people from the global deny list as well?
AFAICT, he's not in any of the list-specific deny lists, only the
global one so I'm not sure if gcc-patches-owner would have worked.
Thanks
--Angela
next reply other threads:[~2004-03-02 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 2:48 Angela Marie Thomas [this message]
2004-03-02 3:10 ` Ian Lance Taylor
2004-03-02 3:16 ` Angela Marie Thomas
2004-03-02 13:45 ` Christopher Faylor
2004-03-02 13:42 ` Christopher Faylor
2004-03-02 14:45 ` 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=20040302025912.27BE7E3A67@foam.wonderslug.com \
--to=angela@foam.wonderslug.com \
--cc=angela@wonderslug.com \
--cc=overseers@sources.redhat.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).