From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 3/7] Clean up opaque-type-resolution help
Date: Tue, 11 Jun 2024 08:54:26 +0300 [thread overview]
Message-ID: <86v82g6n3h.fsf@gnu.org> (raw)
In-Reply-To: <20240610-doc-string-cols-v2-3-5cc5af186d4b@adacore.com> (message from Tom Tromey on Mon, 10 Jun 2024 13:50:24 -0600)
> From: Tom Tromey <tromey@adacore.com>
> Date: Mon, 10 Jun 2024 13:50:24 -0600
>
> The opaque-type-resolution help says "if set before loading symbols",
> but I don't think this is accurate. As far as I know, this resolution
> can be done at any time.
>
> This patch cleans up the help, also shortening it to less than 80
> characters.
> ---
> gdb/gdbtypes.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Thanks, this is okay.
Approved-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2024-06-11 5:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 19:50 [PATCH v2 0/7] Require help text to fit in 80 columns Tom Tromey
2024-06-10 19:50 ` [PATCH v2 1/7] Call gdbpy_fix_doc_string_indentation for function help Tom Tromey
2024-06-10 19:50 ` [PATCH v2 2/7] Wrap help strings at 80 columns Tom Tromey
2024-06-11 6:07 ` Eli Zaretskii
2024-06-11 6:51 ` Metzger, Markus T
2024-06-10 19:50 ` [PATCH v2 3/7] Clean up opaque-type-resolution help Tom Tromey
2024-06-11 5:54 ` Eli Zaretskii [this message]
2024-06-10 19:50 ` [PATCH v2 4/7] Remove the "title" from the remote packet help Tom Tromey
2024-06-11 5:58 ` Eli Zaretskii
2024-06-10 19:50 ` [PATCH v2 5/7] Shorten internal problem help text Tom Tromey
2024-06-11 5:57 ` Eli Zaretskii
2024-06-10 19:50 ` [PATCH v2 6/7] Wrap help options when building help string Tom Tromey
2024-06-10 19:50 ` [PATCH v2 7/7] Ensure that help text fits in 80 columns Tom Tromey
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=86v82g6n3h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).