public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jsm28@cam.ac.uk, nobody@gcc.gnu.org Subject: Re: other/1494: Residual EGCS references in comments Date: Sat, 28 Dec 2002 11:01:00 -0000 [thread overview] Message-ID: <20021228190129.26379.qmail@sources.redhat.com> (raw) Synopsis: Residual EGCS references in comments State-Changed-From-To: feedback->analyzed State-Changed-By: jsm28 State-Changed-When: Sat Dec 28 11:01:28 2002 State-Changed-Why: These present-tense EGCS references are still present in target files, mostly OpenBSD headers. Some new ones have appeared in the CRIS port. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=1494
next reply other threads:[~2002-12-28 19:01 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-28 11:01 jsm28 [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-13 12:46 Joseph S. Myers 2001-11-12 20:36 rodrigc 2001-11-12 20:28 rodrigc
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=20021228190129.26379.qmail@sources.redhat.com \ --to=jsm28@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=jsm28@cam.ac.uk \ --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).