From: Tom Tromey <tromey@adacore.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Fix two varobj bugs
Date: Thu, 07 Sep 2023 13:40:57 -0600 [thread overview]
Message-ID: <87r0n9lqk6.fsf@tromey.com> (raw)
In-Reply-To: <a683757f-c390-4a99-8ec0-8bde98a10e7d@redhat.com> (Keith Seitz's message of "Fri, 1 Sep 2023 10:34:04 -0700")
>> This series fixes a couple of small varobj bugs, and includes a couple
>> small cleanups as well.
>> Regression tested on x86-64 Fedora 36.
Keith> I've looked over this series, and I don't see any issues.
Keith> Reviewed-by: Keith Seitz <keiths@redhat.com>
Thanks, I'm checking this in.
Tom
prev parent reply other threads:[~2023-09-07 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 14:47 Tom Tromey
2023-09-01 14:47 ` [PATCH 1/4] Allow pretty-printer 'children' method to return strings Tom Tromey
2023-09-01 14:47 ` [PATCH 2/4] Remove dead code from varobj_set_display_format Tom Tromey
2023-09-01 14:47 ` [PATCH 3/4] Remove variable_default_display Tom Tromey
2023-09-01 14:47 ` [PATCH 4/4] Fix bug in -var-evaluate-expression Tom Tromey
2023-09-01 17:34 ` [PATCH 0/4] Fix two varobj bugs Keith Seitz
2023-09-07 19:40 ` Tom Tromey [this message]
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=87r0n9lqk6.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).