From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Remove obsolete text from documentation
Date: Thu, 19 May 2022 08:45:23 -0600 [thread overview]
Message-ID: <20220519144523.2365621-1-tromey@adacore.com> (raw)
The documentation says that -enable-pretty-printing is experimental in
7.0 and may change -- that's long enough ago that I think we can say
that this text is no longer correct or useful.
---
gdb/doc/gdb.texinfo | 3 ---
1 file changed, 3 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 8cf97866ccc..b15c8df8c8d 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -33492,9 +33492,6 @@ Once enabled, this feature cannot be disabled.
Note that if Python support has not been compiled into @value{GDBN},
this command will still succeed (and do nothing).
-This feature is currently (as of @value{GDBN} 7.0) experimental, and
-may work differently in future versions of @value{GDBN}.
-
@subheading The @code{-var-create} Command
@findex -var-create
--
2.34.1
next reply other threads:[~2022-05-19 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 14:45 Tom Tromey [this message]
2022-05-19 15:55 ` 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=20220519144523.2365621-1-tromey@adacore.com \
--to=tromey@adacore.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).