From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: mi-break.exp intermitent failure
Date: Wed, 11 Jun 2008 17:11:00 -0000 [thread overview]
Message-ID: <200806111448.09065.pedro@codesourcery.com> (raw)
In-Reply-To: <g2okhb$2ti$1@ger.gmane.org>
A Wednesday 11 June 2008 14:38:56, Vladimir Prus wrote:
> As I've told on IRC, the test should be using mi_expect_stop; I've no idea
> why I did not covert it when I've introduced mi_expect_stop but I've
> checked in the following patch. Can you check that no unexpected
> failures happen for you now.
All perfect. Thanks!
--
Pedro Alves
prev parent reply other threads:[~2008-06-11 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 13:39 Pedro Alves
2008-06-11 14:07 ` Vladimir Prus
2008-06-11 17:11 ` Pedro Alves [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=200806111448.09065.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@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