From: Pedro Alves <pedro@codesourcery.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Implement =thread-selected notification.
Date: Thu, 13 Nov 2008 16:22:00 -0000 [thread overview]
Message-ID: <200811131427.26217.pedro@codesourcery.com> (raw)
In-Reply-To: <200811131714.14566.vladimir@codesourcery.com>
> Seems like this condition is a little bit more messed up than that.
I can't claim I undertand 100% that new command->thread bit, that I'll
trust you on that. :-)
> I attach a reworked patch.
Thanks, I'm happy with this.
--
Pedro Alves
next prev parent reply other threads:[~2008-11-13 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 23:20 Vladimir Prus
2008-11-13 5:08 ` Eli Zaretskii
2008-11-13 8:54 ` Pedro Alves
2008-11-13 11:26 ` Pedro Alves
2008-11-13 15:53 ` Vladimir Prus
2008-11-13 16:22 ` Pedro Alves [this message]
2008-11-13 19:19 ` 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=200811131427.26217.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--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