From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Bob Rossi <bob@brasko.net>, Mark Kettenis <kettenis@gnu.org>,
gdb@sourceware.org
Subject: Re: MI-related testsuite regressions
Date: Mon, 27 Jun 2005 20:53:00 -0000 [thread overview]
Message-ID: <17088.26499.347383.779593@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050627143110.GA31108@nevyn.them.org>
Daniel Jacobowitz writes:
> On Tue, Jun 28, 2005 at 02:08:22AM +1200, Nick Roberts wrote:
> > If thats the case, shouldn't the code read:
> >
...
> >
> > as it stands the mi-*.exp don't test mi3.
>
> Probably, but I don't see much point in changing that until we have
> some content for mi3.
This could equally be said for having separate tests mi-*.exp and mi2-*.exp.
Nick
next prev parent reply other threads:[~2005-06-27 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 8:16 Mark Kettenis
2005-06-27 12:00 ` Nick Roberts
2005-06-27 13:00 ` Daniel Jacobowitz
2005-06-27 13:53 ` Nick Roberts
2005-06-27 13:56 ` Bob Rossi
2005-06-27 13:59 ` Daniel Jacobowitz
2005-06-27 14:07 ` Nick Roberts
2005-06-27 14:31 ` Daniel Jacobowitz
2005-06-27 20:53 ` Nick Roberts [this message]
2005-06-27 21:03 ` 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=17088.26499.347383.779593@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob@brasko.net \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=kettenis@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: 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