From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: yao@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] define and check itset
Date: Thu, 31 May 2012 15:37:00 -0000 [thread overview]
Message-ID: <83ipfc1hwk.fsf@gnu.org> (raw)
In-Reply-To: <4FC7734E.5020401@redhat.com>
> Date: Thu, 31 May 2012 14:34:06 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: gdb-patches@sourceware.org
>
> On 05/31/2012 02:14 PM, Yao Qi wrote:
>
> > This patch is almost from Pedro's patch, with some minor fixes for the
> > new GDB code base and removal of command 'itfocus'.
>
>
> What good does it do to put this in ahead of its prerequisites?
> Can we please stop trying to put the cart before the horse?
> I'm trying to help with the async stuff, but the constant push
> in trying to put other bits in first frustrates me. :-/
>
> The itsets bits need to be last. I'm not even sure the syntax is
> what we want to end up with at all. Last I touched them, I had
> wanted to spend a while trying to unify the concept of "current
> thread" with the itset. There's a disconnect that gets in the
> way a bit.
Should I refrain from reviewing the docs bits for the time being,
then?
next prev parent reply other threads:[~2012-05-31 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 13:15 [PATCH 0/3] Basic ITSET Yao Qi
2012-05-31 13:15 ` [PATCH 1/3] define and check itset Yao Qi
2012-05-31 13:34 ` Pedro Alves
2012-05-31 14:25 ` Yao Qi
2012-05-31 14:51 ` Pedro Alves
2012-05-31 15:37 ` Eli Zaretskii [this message]
2012-05-31 13:15 ` [PATCH 3/3] Doc Yao Qi
2012-05-31 13:15 ` [PATCH 2/3] Test case: gdb.base/itset.exp and gdb.multi/itset.exp Yao Qi
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=83ipfc1hwk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=yao@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