From: Lancelot SIX <lancelot.six@amd.com>
To: gdb-patches@sourceware.org, simon.marchi@efficios.com
Cc: lsix@lancelotsix.com, Lancelot SIX <lancelot.six@amd.com>
Subject: [PATCH 0/1] gdb: Update doc of the "maintenance info line-table"
Date: Wed, 22 Mar 2023 10:26:41 +0000 [thread overview]
Message-ID: <20230322102642.510635-1-lancelot.six@amd.com> (raw)
In-Reply-To: <7c2ba695-c6ec-5854-c81a-e84db28cc66b@simark.ca>
Hi,
It looks like the patch you have pushed is missing the documentation
update for the command. Her is a patch for it.
Best,
Lancelot.
Lancelot SIX (1):
gdb: Update doc of the "maintenance info line-table"
gdb/doc/gdb.texinfo | 32 +++++++++++++++++++-------------
1 file changed, 19 insertions(+), 13 deletions(-)
base-commit: bf3f6c02d73f9823b8cb4f59524f29fbbfb6126d
--
2.34.1
next prev parent reply other threads:[~2023-03-22 10:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 16:30 [PATCH] gdb: make "maintenance info line-table" show relocated addresses again Simon Marchi
2023-03-20 21:35 ` Andrew Burgess
2023-03-21 1:18 ` Simon Marchi
2023-03-21 9:23 ` Andrew Burgess
2023-03-22 1:35 ` Simon Marchi
2023-03-22 10:26 ` Lancelot SIX [this message]
2023-03-22 10:26 ` [PATCH 1/1] gdb: Update doc of the "maintenance info line-table" Lancelot SIX
2023-03-22 13:59 ` Simon Marchi
2023-03-22 16:48 ` Lancelot SIX
2023-03-22 17:20 ` [PATCH v2] " Lancelot SIX
2023-03-22 14:58 ` [PATCH 1/1] " Eli Zaretskii
2023-03-22 13:46 ` [PATCH] gdb: make "maintenance info line-table" show relocated addresses again Tom de Vries
2023-03-22 13:47 ` Simon Marchi
2023-03-22 15:17 ` [PATCH] gdb/testsuite: adjust test cases to previous "maintenance info line-table" change Simon Marchi
2023-03-22 18:01 ` Tom de Vries
2023-03-22 19:14 ` Simon Marchi
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=20230322102642.510635-1-lancelot.six@amd.com \
--to=lancelot.six@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--cc=simon.marchi@efficios.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).