Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC v5] fix regressions with target-async
Date: Wed, 12 Mar 2014 19:04:00 -0000	[thread overview]
Message-ID: <87wqfzkzm4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <532096DD.2020201@redhat.com> (Pedro Alves's message of "Wed, 12	Mar 2014 17:18:21 +0000")

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Pedro> This is OK, please push it in.

Thanks.

Pedro> So in the end, after the target-async series, I think we should go
Pedro> through non-MI tests and remove all that do "set target-async on".

That approach is fine with me too.  Then you can remove the odd linkage
between the "maint" and target-async settings.

Tom


  reply	other threads:[~2014-03-12 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 16:42 Tom Tromey
2014-03-12 17:18 ` Pedro Alves
2014-03-12 19:04   ` Tom Tromey [this message]
2014-03-12 19:27     ` Pedro Alves
2014-03-12 19:46       ` Tom Tromey

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=87wqfzkzm4.fsf@fleche.redhat.com \
    --to=tromey@redhat.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