From: Nicola Pero <nicola@brainstorm.co.uk>
To: overseers@sources.redhat.com
Subject: gnats write access
Date: Wed, 03 Jul 2002 18:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0207040250150.13809-100000@nicola.brainstorm.co.uk> (raw)
Hi,
I've got CVS write access to gcc already (I'm particularly interested in
objc) but once I fix bugs, I can't close them on GNATS :-(
I tried the procedure described in
http://gcc.gnu.org/gnatswrite.html
to get GNATS write access, but it didn't work ... if I put 'GNATS access
only' in the ssh key part, the form is refused.
Can you look at the problem ?
Thanks.
next reply other threads:[~2002-07-04 1:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 18:54 Nicola Pero [this message]
2002-07-03 19:02 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2003-02-23 20:43 GNATS " Richard Sandiford
2003-03-16 14:40 ` Gerald Pfeifer
2002-03-20 11:22 Diego Novillo
2001-12-31 19:40 Colin Howell
2001-04-05 18:21 ` Colin Howell
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-03-05 7:21 Antony Bowers
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
2000-12-30 6:08 GNATS " 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 Joe Buck
2000-11-03 11:33 ` Joe Buck
2000-12-30 6:08 ` Gerald Pfeifer
2000-11-03 12:08 ` Gerald Pfeifer
2000-12-30 6:08 ` Jeffrey A Law
2000-12-05 20:24 ` Jeffrey A Law
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 ` Tom Tromey
2000-11-03 12:34 ` 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.LNX.4.21.0207040250150.13809-100000@nicola.brainstorm.co.uk \
--to=nicola@brainstorm.co.uk \
--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).