From: Jeffrey A Law <law@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: rodrigc@mediaone.net, overseers@gcc.gnu.org, pfeifer@dbai.tuwien.ac.at
Subject: Re: GNATS access
Date: Mon, 19 Feb 2001 09:04:00 -0000 [thread overview]
Message-ID: <26175.982602340@slagheap.cygnus.com> (raw)
In-Reply-To: <20010219085252W.mitchell@codesourcery.com>
In message < 20010219085252W.mitchell@codesourcery.com >you write:
> Jeff, is it OK to change the `gnastwrite' page to point directly to
> the account set-up page you referenced?
Sure. Actually, any page we have which is related to setting up accounts
can point to that page.
> 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?
Sounds fine to me.
jeff
next prev parent reply other threads:[~2001-02-19 9:04 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
2001-02-19 9:04 ` Jeffrey A Law [this message]
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=26175.982602340@slagheap.cygnus.com \
--to=law@redhat.com \
--cc=mark@codesourcery.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).