From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [MI non-stop 0/11] Series overview
Date: Sat, 28 Jun 2008 17:33:00 -0000 [thread overview]
Message-ID: <ud4m1cvzu.fsf@gnu.org> (raw)
In-Reply-To: <200806282033.28441.vladimir@codesourcery.com>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sat, 28 Jun 2008 20:33:27 +0400
>
>
> I'm about to post, finally, the set of patches that add MI-side support for
> non-stop behaviour. The only dependency is Pedro's core non-stop set.
>
> Actually, Pedro's patches already make basic non-stop
> mode work in MI, and my patches address various, mostly independent,
> issues that are still important to get a frontend that work well.
>
> All patches are ready to be committed, except the patch for enabling non-stop
> with a single command -- that one needs discussion.
What about documenting the new features?
next prev parent reply other threads:[~2008-06-28 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 16:38 Vladimir Prus
2008-06-28 17:33 ` Eli Zaretskii [this message]
2008-06-28 17:35 ` Vladimir Prus
2008-06-28 18:11 ` Stan Shebs
2008-06-29 5:38 ` Vladimir Prus
2008-06-28 18:20 ` Eli Zaretskii
2008-06-29 5:47 ` Vladimir Prus
2008-06-29 17:49 ` Eli Zaretskii
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=ud4m1cvzu.fsf@gnu.org \
--to=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