public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: ada/5905: Nag message code considered harmful Date: Sun, 06 Oct 2002 07:26:00 -0000 [thread overview] Message-ID: <20021006142600.15278.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/5905; it has been noted by GNATS. From: Andreas Jaeger <aj@suse.de> To: "Joseph S. Myers" <jsm28@cam.ac.uk> Cc: <bosch@gcc.gnu.org>, <fw@deneb.enyo.de>, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: ada/5905: Nag message code considered harmful Date: Sun, 06 Oct 2002 14:28:30 +0200 "Joseph S. Myers" <jsm28@cam.ac.uk> writes: > On 5 Oct 2002 bosch@gcc.gnu.org wrote: > >> This is fixed in current sources. > > No, it isn't; it's only been fixed on the 3.1 branch, and is on the > possibly incomplete list of such patches in ada/6919. I suggest to reopen the PR, Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj
next reply other threads:[~2002-10-06 14:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-06 7:26 Andreas Jaeger [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-06 2:16 Joseph S. Myers 2002-10-05 16:31 bosch 2002-03-10 1:56 fw
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=20021006142600.15278.qmail@sources.redhat.com \ --to=aj@suse.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).