Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
	"'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [MI] Duplicate --thread-group flag not detected
Date: Thu, 02 Dec 2010 17:10:00 -0000	[thread overview]
Message-ID: <20101202170954.GA3031@adacore.com> (raw)
In-Reply-To: <m3bp54ku1x.fsf@fleche.redhat.com>

> I think in this case the patch is simple and obvious enough that we can
> go forward without waiting.
> 
> What do you think of that?

Agreed. I am also OK for the 7.2 branch, even if it's not exactly
a critical bug.

> I was curious about this -- is this sort of transition something people
> would want to see done?  Would it help MI users?  (It would help Python
> if we ever implemented the automatic MI wrapping... but I am not sure
> whether we really want to do that.)

I hope others have enough experience with MI that we can have some
useful answers. I don't have much experience with MI myself...


-- 
Joel


  reply	other threads:[~2010-12-02 17:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 20:56 Marc Khouzam
2010-11-26 16:39 ` Joel Brobecker
2010-12-02 16:40   ` Tom Tromey
2010-12-02 17:10     ` Joel Brobecker [this message]
2010-12-04 18:10       ` Marc Khouzam
2010-12-04 18:47         ` Joel Brobecker
2010-12-05 19:27           ` Marc Khouzam
2010-12-06 11:04             ` Joel Brobecker
2010-12-06 14:26               ` Marc Khouzam
2010-12-06 15:02               ` [MI] --thread-group test (was: RE: [MI] Duplicate --thread-group flag not detected) Marc Khouzam
2010-12-10 12:15                 ` Joel Brobecker

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=20101202170954.GA3031@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=tromey@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