Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] define and check itset
Date: Thu, 31 May 2012 14:25:00 -0000	[thread overview]
Message-ID: <4FC77EDB.8040005@codesourcery.com> (raw)
In-Reply-To: <4FC7734E.5020401@redhat.com>

On 05/31/2012 09:34 PM, Pedro Alves wrote:
> 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.  :-/
> 

I don't want to frustrates anyone here.  This bit doesn't have any
prerequisites, as I said, it is quite isolated from other parts.  I
don't see anything wrong this bits go in first.  The review process to
patch series 'run all-stop on top of non-stop' is not smooth, which
forces me to start to push this part first.

> 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.

I don't know your plan, and you are free to change whatever you'd like
to.  AFAICS, the syntax looks fine to me, so I posted them.

-- 
Yao (齐尧)


  reply	other threads:[~2012-05-31 14:25 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 [this message]
2012-05-31 14:51       ` Pedro Alves
2012-05-31 15:37     ` Eli Zaretskii
2012-05-31 13:15 ` [PATCH 2/3] Test case: gdb.base/itset.exp and gdb.multi/itset.exp Yao Qi
2012-05-31 13:15 ` [PATCH 3/3] Doc 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=4FC77EDB.8040005@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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