From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Minor doc fix for Python Type.fields
Date: Wed, 05 Nov 2025 21:30:34 +0200 [thread overview]
Message-ID: <86o6pge0px.fsf@gnu.org> (raw)
In-Reply-To: <20251105181059.3444537-1-tromey@adacore.com> (message from Tom Tromey on Wed, 5 Nov 2025 11:10:59 -0700)
> From: Tom Tromey <tromey@adacore.com>
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Wed, 5 Nov 2025 11:10:59 -0700
>
> This changes the Python Type.fields documentation in a few minor ways:
>
> * Documents that a new sequence is always returned I've intentionally
> not mentioned that it is currently a list, in case we want to change
> to a tuple someday.
>
> * Move the C++ base class note to the bullet about structure types,
> where it makes more sense.
>
> * Added a blank line before the table to make the info page easier to
> read.
> ---
> gdb/doc/python.texi | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
This is okay, thanks.
Approved-By: Eli Zaretskii <eliz@gnu.org>
prev parent reply other threads:[~2025-11-05 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 18:10 Tom Tromey
2025-11-05 18:29 ` Paul Koning
2025-11-05 19:05 ` Tom Tromey
2025-11-05 19:21 ` Paul Koning
2025-11-05 19:27 ` Tom Tromey
2025-11-05 19:30 ` Paul Koning
2025-11-05 19:30 ` Eli Zaretskii [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=86o6pge0px.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