From: Joel Brobecker <brobecker@adacore.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: arrayidx.exp failures
Date: Fri, 13 Oct 2006 20:10:00 -0000 [thread overview]
Message-ID: <20061013201005.GK1059@adacore.com> (raw)
In-Reply-To: <17711.57150.711484.769763@kahikatea.snap.net.nz>
> It's not an issue for those of us who don't use Ada but it might be
> one for you, in that we might not notice our changes have broken the
> Ada tests if they are already broken for us.
That's perfectly fine. We all do our best, and even when the FSF GCC is
better, some people may not have it installed and stil potentially break
some of the Ada testcases. I try to check the results on a regular
basis to catch such unavoidable mishaps.
--
Joel
next prev parent reply other threads:[~2006-10-13 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 2:17 Nick Roberts
2006-10-13 2:38 ` Joel Brobecker
2006-10-13 4:39 ` Daniel Jacobowitz
2006-10-13 16:34 ` Joel Brobecker
2006-10-13 18:50 ` Nick Roberts
2006-10-13 20:10 ` Joel Brobecker [this message]
2006-10-13 22:06 ` Daniel Jacobowitz
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=20061013201005.GK1059@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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