From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PUSHED 0/3] Re: [PATCH] Fix inconsistent input/output of example
Date: Thu, 19 May 2022 15:24:31 +0100 [thread overview]
Message-ID: <cover.1652970188.git.aburgess@redhat.com> (raw)
In-Reply-To: <CAAQmekeQ=8B1gFDSHMyzjcm6moYuqbdLn+qJ03OX8-mZZARXew@mail.gmail.com>
Nikolaos Chatzikonstantinou,
Thanks, I pushed your patch. While applying this I spotted some
additional improvements that could be made to the 'info
pretty-printer' example, so I pushed those too.
Here's what I applied.
Thanks,
Andrew
---
Andrew Burgess (2):
gdb/doc: make use of group/end group in 'info pretty-printers' example
gdb/doc: use @value{GDBP} in 'info pretty-printer' example
Nikolaos Chatzikonstantinou (1):
gdb/doc: fix inconsistent info pretty-printer example
gdb/doc/gdb.texinfo | 28 ++++++++++++++++++----------
1 file changed, 18 insertions(+), 10 deletions(-)
--
2.25.4
next prev parent reply other threads:[~2022-05-19 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 13:35 Nikolaos Chatzikonstantinou
2022-05-18 15:30 ` Andrew Burgess
2022-05-18 21:14 ` Nikolaos Chatzikonstantinou
2022-05-19 14:24 ` Andrew Burgess [this message]
2022-05-19 14:24 ` [PUSHED 1/3] gdb/doc: fix inconsistent info pretty-printer example Andrew Burgess
2022-05-19 14:24 ` [PUSHED 2/3] gdb/doc: make use of group/end group in 'info pretty-printers' example Andrew Burgess
2022-05-19 14:24 ` [PUSHED 3/3] gdb/doc: use @value{GDBP} in 'info pretty-printer' example Andrew Burgess
2022-05-19 15:54 ` [PUSHED 0/3] Re: [PATCH] Fix inconsistent input/output of example Eli Zaretskii
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=cover.1652970188.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/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).