public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: overseers@sourceware.cygnus.com
Subject: GNATS access
Date: Mon, 07 Aug 2000 08:46:00 -0000	[thread overview]
Message-ID: <14555.965663204@upchuck> (raw)
Message-ID: <20000807084600.n0Xa2xHSoRp7J6jDQ8-6W4oo2BrQBOVSe7CakxNe0xI@z> (raw)

I don't know how to handle this myself...


------- Forwarded Message

Sender:   "Joseph S. Myers" <jsm28@hermes.cam.ac.uk>
From:     "Joseph S. Myers" <jsm28@cam.ac.uk>
To:       Jeffrey A Law <law@cygnus.com>
Date:     Fri, 4 Aug 2000 21:32:44 +0100 (BST)
Subject:  Re: CVS Write Access 

On Fri, 4 Aug 2000, Jeffrey A Law wrote:

> http://gcc.gnu.org/cvswrite.html

 ... which says

> Maintainers are also encouraged to edit the GNATS database.

So, can I have a GNATS password to do so?  There are presently about five
open C PRs in the database fixed by my past patches, and another five or
so I've identified as being non-bugs that can be closed or marked as
change-requests.

- -- 
Joseph S. Myers
jsm28@cam.ac.uk



------- End of Forwarded Message



             reply	other threads:[~2000-08-07  8:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Jeffrey A Law [this message]
2000-08-07  8:46 ` Jeffrey A Law
2000-12-30  6:08 ` Tom Tromey
2000-08-07  9:19   ` Tom Tromey
     [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
2001-02-19 16:35             ` Craig Rodrigues
2001-02-22 18:05             ` Craig Rodrigues

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=14555.965663204@upchuck \
    --to=law@cygnus.com \
    --cc=overseers@sourceware.cygnus.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).