From: Craig Rodrigues <rodrigc@mediaone.net>
To: overseers@gcc.gnu.org
Cc: pfeifer@dbai.tuwien.ac.at, mark@codesourcery.com
Subject: Re: GNATS access
Date: Sun, 18 Feb 2001 20:34:00 -0000 [thread overview]
Message-ID: <20010218233316.A13454@mediaone.net> (raw)
In-Reply-To: <20010218195852D.mitchell@codesourcery.com>
Hi,
As directed, I am sending this e-mail to this address.
I am offering to clear out some of the C++ related
bug reports in GNATS, with the hope that my efforts
will help the GCC developers release a high quality
GCC 3.0.
What should I do to get set up?
I've already looked at about 100 reports.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@mediaone.net
On Sun, Feb 18, 2001 at 07:58:52PM -0800, Mark Mitchell wrote:
> >>>>> "Craig" == Craig Rodrigues <rodrigc@mediaone.net> writes:
>
> Craig> Mark,
>
> Craig> I've been trying to clear C++ bug reports in GNATS in the
> Craig> past few days, in order to assist GCC developers in
> Craig> releasing a high quality GCC 3.0.
>
> Craig> How can I get access to GNATS in order to help out?
>
> Thanks for volunteering!
>
> Please follow the directions at http://gcc.gnu.org/gnatswrite.html .
>
> In particular, please send mail to `overseers@gcc.gnu.org' to get an
> account set up.
>
> Thanks,
>
> --
> Mark Mitchell mark@codesourcery.com
> CodeSourcery, LLC http://www.codesourcery.com
next parent reply other threads:[~2001-02-18 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010218190201.A12663@mediaone.net>
[not found] ` <Pine.BSF.4.33.0102190118320.67648-100000@deneb.dbai.tuwien.ac.at>
[not found] ` <20010218201818.A13224@mediaone.net>
[not found] ` <20010218195852D.mitchell@codesourcery.com>
2001-02-18 20:34 ` Craig Rodrigues [this message]
2001-02-19 8:35 ` Jeffrey A Law
2001-02-19 8:47 ` Mark Mitchell
2001-02-19 9:04 ` Jeffrey A Law
2001-02-19 16:35 ` Craig Rodrigues
2001-02-22 18:05 ` Craig Rodrigues
2000-12-30 6:08 Jeffrey A Law
2000-08-07 8:46 ` Jeffrey A Law
2000-12-30 6:08 ` Tom Tromey
2000-08-07 9:19 ` 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=20010218233316.A13454@mediaone.net \
--to=rodrigc@mediaone.net \
--cc=mark@codesourcery.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).