From: Mark Mitchell <mark@codesourcery.com>
To: law@redhat.com
Cc: rodrigc@mediaone.net, overseers@gcc.gnu.org, pfeifer@dbai.tuwien.ac.at
Subject: Re: GNATS access
Date: Mon, 19 Feb 2001 08:47:00 -0000 [thread overview]
Message-ID: <20010219085252W.mitchell@codesourcery.com> (raw)
In-Reply-To: <26011.982600615@slagheap.cygnus.com>
We're putting poor Craig through a lot of steps, which isn't the best
way to encourage a willing volunteer.
Jeff, is it OK to change the `gnastwrite' page to point directly to
the account set-up page you referenced?
If so, I would suggest that Gerald make the following change to the
gnatswrite page to explain that you will first need to get approval
from someone on the GCC steering committee. For now, I'm happy to be
the designated representative. The instructions should say something
like:
First send mail to <...> indicating that you would like to
have GNATS write access. Please explain why you would like
to have write access. If your request is approved, you should
then visit:
http://sourceware.cygnus.com/cgi-bin/pdw/ps_form.cgi
Does that sound OK to everyone?
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2001-02-19 8:47 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
2001-02-19 8:35 ` Jeffrey A Law
2001-02-19 8:47 ` Mark Mitchell [this message]
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=20010219085252W.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=law@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=rodrigc@mediaone.net \
/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).