From: Tom Tromey <tom@tromey.com>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix ptype/o bug with "<no data fields>"
Date: Thu, 22 Apr 2021 19:39:15 -0600 [thread overview]
Message-ID: <87czulg4os.fsf@tromey.com> (raw)
In-Reply-To: <20210422214553.pkvxsgnotuftuwgt@Plymouth> (Lancelot SIX's message of "Thu, 22 Apr 2021 22:45:53 +0100")
Tom> Thanks. I think I'll hold this one until the other ptype/o patches
Tom> land.
>> I think you are referring to my ptype patch
>> (https://sourceware.org/pipermail/gdb-patches/2021-April/177841.html)
>> which still needs to be approved for the documentation part.
Yep.
I didn't check if Eli approved the docs in v1. If so then you're good.
>> I do not mind reworking it to take into account this patch if it lands
>> in master first. It should only have conflicts on the tests, which will
>> be easy to fix.
Ok, thanks, I will go ahead.
Probably the test just needs a few spaces added.
Tom
next prev parent reply other threads:[~2021-04-23 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 1:49 Tom Tromey
2021-04-22 9:31 ` Andrew Burgess
2021-04-22 13:17 ` Tom Tromey
2021-04-22 21:45 ` Lancelot SIX via Gdb-patches
2021-04-23 1:39 ` Tom Tromey [this message]
2021-04-23 6:12 ` Eli Zaretskii via Gdb-patches
2021-04-23 10:41 ` Lancelot SIX via Gdb-patches
2021-04-23 11:03 ` Eli Zaretskii via Gdb-patches
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=87czulg4os.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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