From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: <overseers@sources.redhat.com>
Cc: Joe Buck <jbuck@racerx.synopsys.com>
Subject: Re: GNATS write access
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.30.0011032103330.38006-100000@taygeta.dbai.tuwien.ac.at> (raw)
In-Reply-To: <200011031927.LAA18439@racerx.synopsys.com>
On Fri, 3 Nov 2000, Joe Buck wrote:
> I need to have GNATS write access. Mark Mitchell pointed me to
> "overseers". Can someone set this up?
Folks, I'll take care of it.
A general question: Do new GCC contributors now automatically get a
GNATS account set up from the beginning?
If so, we don't need to document the procedure how to obtain one on
the web, else we should (and I'm going to do so).
In this case, can I mention the overseers address there? If so, can
we have an alias overseers@gcc.gnu.org, please? (Trust me, this will
save a couple of us some undesirable discussions later on... :-/)
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
WARNING: multiple messages have this Message-ID
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: <overseers@sources.redhat.com>
Cc: Joe Buck <jbuck@racerx.synopsys.com>
Subject: Re: GNATS write access
Date: Fri, 03 Nov 2000 12:08:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.30.0011032103330.38006-100000@taygeta.dbai.tuwien.ac.at> (raw)
Message-ID: <20001103120800.DJFG0eqqXZnGYJCs9-7fJthem73oOXdwJY7NyniKY2o@z> (raw)
In-Reply-To: <200011031927.LAA18439@racerx.synopsys.com>
On Fri, 3 Nov 2000, Joe Buck wrote:
> I need to have GNATS write access. Mark Mitchell pointed me to
> "overseers". Can someone set this up?
Folks, I'll take care of it.
A general question: Do new GCC contributors now automatically get a
GNATS account set up from the beginning?
If so, we don't need to document the procedure how to obtain one on
the web, else we should (and I'm going to do so).
In this case, can I mention the overseers address there? If so, can
we have an alias overseers@gcc.gnu.org, please? (Trust me, this will
save a couple of us some undesirable discussions later on... :-/)
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Joe Buck
2000-11-03 11:33 ` Joe Buck
2000-12-30 6:08 ` Gerald Pfeifer [this message]
2000-11-03 12:08 ` Gerald Pfeifer
2000-12-30 6:08 ` Jeffrey A Law
2000-11-06 8:11 ` Jeffrey A Law
2000-12-30 6:08 ` Gerald Pfeifer
2000-11-06 12:30 ` Gerald Pfeifer
2000-12-30 6:08 ` Jeffrey A Law
2000-12-05 20:24 ` Jeffrey A Law
2000-12-30 6:08 ` Tom Tromey
2000-11-03 12:34 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2003-02-23 20:43 Richard Sandiford
2003-03-16 14:40 ` Gerald Pfeifer
2002-07-03 18:54 gnats " Nicola Pero
2002-07-03 19:02 ` Christopher Faylor
2002-03-20 11:22 GNATS " Diego Novillo
2001-12-31 19:40 James Dennett
2001-02-12 16:48 ` James Dennett
2001-12-31 19:40 ` Phil Edwards
2001-02-12 17:04 ` Phil Edwards
2001-12-31 19:40 ` Christopher Faylor
2001-02-12 17:17 ` Christopher Faylor
2001-12-31 19:40 ` James Dennett
2001-02-12 17:24 ` James Dennett
2001-12-31 19:40 Colin Howell
2001-04-05 18:21 ` Colin Howell
2001-03-05 7:21 Antony Bowers
2000-12-30 6:08 Jeffrey A Law
2000-10-10 11:15 ` Jeffrey A Law
2000-12-30 6:08 ` Gerald Pfeifer
2000-10-10 11:28 ` Gerald Pfeifer
2000-12-30 6:08 gnats " Richard Henderson
2000-11-28 16:26 ` Richard Henderson
2000-12-30 6:08 ` Jeffrey A Law
2000-11-28 17:47 ` Jeffrey A Law
2000-12-30 6:08 ` Tom Tromey
2000-11-28 17:40 ` Tom Tromey
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=Pine.BSF.4.30.0011032103330.38006-100000@taygeta.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=jbuck@racerx.synopsys.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).