From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCHv3] gdb: add support for %V to printf command
Date: Tue, 30 May 2023 21:56:43 +0100 [thread overview]
Message-ID: <875y895yic.fsf@redhat.com> (raw)
In-Reply-To: <87r0r2x1p5.fsf@tromey.com>
Tom Tromey <tom@tromey.com> writes:
>>>>>> "Andrew" == Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Andrew> - Still need to check that Tom's query is satisfied (see V2 email):
> Andrew> https://sourceware.org/pipermail/gdb-patches/2023-April/199178.html
>
> It is. Thank you for doing this.
Excellent. I went ahead and pushed this.
>
> Also, it turns out this will be handy for DAP, to implement the
> logMessage support.
Glad this helps!
Thanks,
Andrew
prev parent reply other threads:[~2023-05-30 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 12:22 [PATCH] " Andrew Burgess
2023-03-30 14:20 ` Eli Zaretskii
2023-04-11 12:34 ` Andrew Burgess
2023-04-17 15:47 ` Tom Tromey
2023-04-28 13:14 ` [PATCHv2] " Andrew Burgess
2023-04-28 15:34 ` Eli Zaretskii
2023-05-12 13:01 ` [PATCHv3] " Andrew Burgess
2023-05-12 13:47 ` Simon Marchi
2023-05-26 20:44 ` Tom Tromey
2023-05-30 20:56 ` Andrew Burgess [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=875y895yic.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).