Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org,  Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH] Remove excess calls to gdb_flush
Date: Tue, 05 Mar 2019 15:56:00 -0000	[thread overview]
Message-ID: <87k1hduxfl.fsf@tromey.com> (raw)
In-Reply-To: <20190219151226.2805c624@f29-4.lan> (Kevin Buettner's message of	"Tue, 19 Feb 2019 15:12:26 -0700")

>>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:

>> I tracked this down to a call to gdb_flush in generic_val_print.
>> Then, I went through all calls to gdb_flush and removed the ones I
>> thought were superfluous.  In particular:
[...]

Kevin> I looked over the patch and didn't see any problems.

Thanks, I'm checking this in now.

Tom


  reply	other threads:[~2019-03-05 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 20:54 Tom Tromey
2019-02-19 22:12 ` Kevin Buettner
2019-03-05 15:56   ` Tom Tromey [this message]
2019-03-05 17:06 ` Pedro Alves
2019-03-05 17:54   ` Tom Tromey
2019-03-07  6:06     ` 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=87k1hduxfl.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=tromey@adacore.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