From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Implement *running.
Date: Thu, 05 Jun 2008 15:50:00 -0000 [thread overview]
Message-ID: <20080605155033.GB29085@caradoc.them.org> (raw)
In-Reply-To: <200805271955.04084.vladimir@codesourcery.com>
On Tue, May 27, 2008 at 07:55:03PM +0400, Vladimir Prus wrote:
> Dan,
> do you have any further comments on this patch, or it's OK to commit?
The code patch is OK with the revised docs.
Why are the *running checks in the testsuite optional - shouldn't it
always be produced now?
I hope you're right that adding *running in mi2 output won't break
frontends :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-06-05 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 13:36 Vladimir Prus
2008-05-02 9:57 ` Eli Zaretskii
2008-05-02 15:59 ` Daniel Jacobowitz
2008-05-04 16:33 ` Vladimir Prus
2008-05-04 19:50 ` Eli Zaretskii
2008-05-11 15:32 ` Vladimir Prus
2008-05-11 21:46 ` Eli Zaretskii
2008-05-27 19:07 ` Vladimir Prus
2008-06-05 15:50 ` Daniel Jacobowitz [this message]
2008-06-10 12:43 ` Vladimir Prus
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=20080605155033.GB29085@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--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