From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: -var-create testsuite updates
Date: Tue, 13 Feb 2007 12:03:00 -0000 [thread overview]
Message-ID: <20070213120234.GA9169@caradoc.them.org> (raw)
In-Reply-To: <17872.13205.858594.311278@kahikatea.snap.net.nz>
On Mon, Feb 12, 2007 at 10:29:57PM +1300, Nick Roberts wrote:
> I prefer to keep the tests simple so that I can remember how they work. I
> generally just use cut and paste anyway.
Another advantage of staying with mi_gdb_test is that if the test
fails, it's easy to see what the .exp file expected.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-13 12:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 16:20 Daniel Jacobowitz
2007-02-09 20:48 ` Nick Roberts
2007-02-09 20:57 ` Daniel Jacobowitz
2007-02-11 21:43 ` Nick Roberts
2007-02-11 21:46 ` Daniel Jacobowitz
2007-02-12 6:18 ` Vladimir Prus
2007-02-12 9:30 ` Nick Roberts
2007-02-13 12:03 ` Daniel Jacobowitz [this message]
2007-02-15 20:55 ` -var-create testsuite updates [PATCH] Nick Roberts
2007-02-27 17:10 ` Daniel Jacobowitz
2007-03-09 1:00 ` Ulrich Weigand
2007-03-09 1:41 ` Nick Roberts
2007-03-09 2:22 ` Ulrich Weigand
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=20070213120234.GA9169@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--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