public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: bosch@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/5856: GNAT bug box
Date: Fri, 18 Oct 2002 17:06:00 -0000 [thread overview]
Message-ID: <20021019000602.4678.qmail@sources.redhat.com> (raw)
The following reply was made to PR ada/5856; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Joe Buck <jbuck@synopsys.com>
Cc: <gcc-gnats@gcc.gnu.org>, <bosch@gcc.gnu.org>, <rodrigc@gcc.gnu.org>,
<gcc-bugs@gcc.gnu.org>
Subject: Re: ada/5856: GNAT bug box
Date: Sat, 19 Oct 2002 01:05:40 +0100 (BST)
On Fri, 18 Oct 2002, Joe Buck wrote:
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5856
>
> I was looking for high-priority bugs that can be closed. It seems we
> can close
> this one, as I can't find any direction to the ACT bug tracking system
> anymore
> in the 3.2 branch. Can this be closed?
This problem is represented by PR ada/6919 - covering patches such as this
that haven't been forward ported from the branch to the mainline. 3.2
branch gives a proper bug box, mainline doesn't (no ACT reference, but
gives email address rather than URL with instructions and has other
problems described in that PR).
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2002-10-19 0:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 17:06 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-18 17:06 Joe Buck
2002-03-10 13:16 Craig Rodrigues
2002-03-09 1:26 Florian Weimer
2002-03-06 17:56 Geert Bosch
2002-03-06 17:25 rodrigc
2002-03-06 13:36 Joseph Myers
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=20021019000602.4678.qmail@sources.redhat.com \
--to=jsm28@cam.ac.uk \
--cc=bosch@gcc.gnu.org \
--cc=gcc-prs@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).