From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] [doc] Update obsolete text about sub-blocks
Date: Thu, 03 Sep 2026 20:45:47 +0300 [thread overview]
Message-ID: <86se3q2ppw.fsf@gnu.org> (raw)
In-Reply-To: <20260903164749.3872468-1-tromey@adacore.com> (message from Tom Tromey on Thu, 3 Sep 2026 10:47:49 -0600)
> From: Tom Tromey <tromey@adacore.com>
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Thu, 3 Sep 2026 10:47:49 -0600
>
> The manual claims that there is no way to iterate over the sub-blocks
> of a gdb.Block, but this hasn't been true since commit 5166ed9c
> ("gdb/python: add subblocks property to gdb.Block").
>
> v2: This patch removes the entire paragraph. After some discussion we
> agreed it was confusing to talk about what gdb can't do.
> ---
> gdb/doc/python.texi | 5 -----
> 1 file changed, 5 deletions(-)
This is okay, thanks.
Approved-By: Eli Zaretskii <eliz@gnu.org>
prev parent reply other threads:[~2026-09-03 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 16:47 Tom Tromey
2026-09-03 17:45 ` 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=86se3q2ppw.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