From: "Joseph S. Myers" <jsm@polyomino.org.uk>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Broken URL in README.QMTEST
Date: Fri, 03 Sep 2004 20:47:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0409032039210.10563@digraph.polyomino.org.uk> (raw)
In-Reply-To: <41380811.40208@codesourcery.com>
On Thu, 2 Sep 2004, Mark Mitchell wrote:
> Fixed with:
>
> 2004-09-02 Mark Mitchell <mark@codesourcery.com>
>
> * README.QMTEST: Fix out-of-date link.
Thanks. (I was looking at QMTest in connection with its potential for
solving the problem that dg-error and dg-warning don't actually
distinguish errors and warnings
<http://gcc.gnu.org/ml/gcc-patches/2003-07/msg01076.html>.)
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
http://www.srcf.ucam.org/~jsm28/gcc/#c90status - status of C90 for GCC 3.5
jsm@polyomino.org.uk (personal mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
prev parent reply other threads:[~2004-09-03 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 15:52 Joseph S. Myers
2004-09-03 5:58 ` Mark Mitchell
2004-09-03 20:47 ` Joseph S. Myers [this message]
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=Pine.LNX.4.61.0409032039210.10563@digraph.polyomino.org.uk \
--to=jsm@polyomino.org.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).