public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: gcc@gcc.gnu.org
Subject: GNATS
Date: Wed, 16 Oct 2002 08:10:00 -0000	[thread overview]
Message-ID: <20021016142725.GA14611@doctormoo.dyndns.org> (raw)

The high-priority bug reports in GNATS could use a good going through.

Some are solved but not closed; others appear to be unreproducible.  Some
are in the wrong categories and some that should be marked 'feedback'
aren't.

I can't get GNATS write access to do this because the instructions for
getting GNATS write access don't work (sources.redhat.com complains about
an improperly formatted identity.pub).

--Nathanael

             reply	other threads:[~2002-10-16 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16  8:10 Nathanael Nerode [this message]
     [not found] ` <Pine.BSF.4.44.0210161634560.22503-100000@naos.dbai.tuwien.ac.at>
2002-10-16  9:21   ` GNATS Nathanael Nerode
2002-10-16 15:05 GNATS Nathanael Nerode
2002-10-16 15:16 ` GNATS Gerald Pfeifer
2002-10-16 22:28   ` GNATS Nathanael Nerode
2002-10-17  6:54 ` GNATS Daniel Berlin

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=20021016142725.GA14611@doctormoo.dyndns.org \
    --to=neroden@doctormoo.dyndns.org \
    --cc=gcc@gcc.gnu.org \
    /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).