From: Christopher Faylor <cgf@redhat.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@gcc.gnu.org
Subject: Re: failure notice (fwd)
Date: Sat, 10 Mar 2001 12:09:00 -0000 [thread overview]
Message-ID: <20010310150912.F975@redhat.com> (raw)
In-Reply-To: <Pine.BSF.4.33.0103100852250.29989-100000@deneb.dbai.tuwien.ac.at>
On Sat, Mar 10, 2001 at 08:54:30AM +0100, Gerald Pfeifer wrote:
>On Fri, 9 Mar 2001, Christopher Faylor wrote:
>> I'm not sure what to do, here. We do have to forward the email to
>> something. We don't want "personal" email accumulating on gcc.gnu.org.
>
>Can we circumvent this security measure easily, for this specific case?
>
> <gcc@gcc.gnu.org>:
> Mail note rejected: List address must be in To: or Cc: headers.
>
>If so, though, my feeling is that overseers@gcc.gnu.org might be a better
>candidate for the forward than gcc@gcc.gnu.org. Unless we find a group of
>volunteers that are taking care of this mail, that is.
I can add gccadmin@gcc.gnu.org as an allowed address for gcc@gcc.gnu.org.
I don't think that overseers@gcc.gnu.org is the appropriate place to send
these, though. I thought that the purpose of this account was to eliminate
the need for involving overseers.
We could set up a gccadmin mailing list or mail alias and let people join
it. Would that be ok?
cgf
next prev parent reply other threads:[~2001-03-10 12:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 15:26 Gerald Pfeifer
2001-03-09 17:11 ` Christopher Faylor
2001-03-09 23:54 ` Gerald Pfeifer
2001-03-10 12:09 ` Christopher Faylor [this message]
2001-03-10 16:54 ` Gerald Pfeifer
2001-07-31 1:06 Bernhard Rosenkraenzer
2001-07-31 9:05 ` Tom Tromey
2002-03-19 10:54 Joseph S. Myers
2002-03-20 8:46 ` Christopher Faylor
2002-05-03 9:55 Joseph S. Myers
2005-04-05 23:55 Joseph S. Myers
2005-04-06 0:30 ` 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=20010310150912.F975@redhat.com \
--to=cgf@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).