public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/10203: version.c: bug_report_url is outdated Date: Tue, 25 Mar 2003 18:46:00 -0000 [thread overview] Message-ID: <20030325184600.29093.qmail@sources.redhat.com> (raw) The following reply was made to PR other/10203; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mmabreu@inf.ufrgs.br, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: other/10203: version.c: bug_report_url is outdated Date: Tue, 25 Mar 2003 10:46:27 -0800 On Tue, Mar 25, 2003 at 03:49:57PM -0000, bangerth@dealii.org wrote: > Synopsis: version.c: bug_report_url is outdated > > State-Changed-From-To: open->analyzed > State-Changed-By: bangerth > State-Changed-When: Tue Mar 25 15:49:56 2003 > State-Changed-Why: > Zack already confirmed this, which I do again hereby. I > think this is really something that we need to clear before > the next release, one way or other, so I raise the priority. Most of the GCC documentation has links to http://gcc.gnu.org. In gcc/doc/*.texi, the only links to http://www.gnu.org are for GNU docs, not mirrored GCC docs. Unless someone complains, I'll apply the patch (mainline and 3.3-branch) and close this PR later today. Janis
next reply other threads:[~2003-03-25 18:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-25 18:46 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-26 1:48 janis 2003-03-25 19:46 Wolfgang Bangerth 2003-03-25 15:50 bangerth 2003-03-25 8:29 Zack Weinberg 2003-03-25 5:26 mmabreu
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=20030325184600.29093.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --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).