From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: RFA: fix menu in python api documentation
Date: Fri, 07 Jan 2011 15:02:00 -0000 [thread overview]
Message-ID: <m3d3o8oiym.fsf@fleche.redhat.com> (raw)
This patch needs a doc review.
I noticed that the @menu in the Python API node was missing a couple of
descriptions. This patch adds them.
Ok?
Tom
2011-01-07 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Python API): Add descriptions to @menu items.
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.786
diff -u -r1.786 gdb.texinfo
--- doc/gdb.texinfo 6 Jan 2011 21:10:52 -0000 1.786
+++ doc/gdb.texinfo 7 Jan 2011 15:01:50 -0000
@@ -20710,8 +20710,8 @@
@menu
* Basic Python:: Basic Python Functions.
-* Exception Handling::
-* Values From Inferior::
+* Exception Handling:: How Python exceptions are translated.
+* Values From Inferior:: Python representation of values.
* Types In Python:: Python representation of types.
* Pretty Printing API:: Pretty-printing values.
* Selecting Pretty-Printers:: How GDB chooses a pretty-printer.
next reply other threads:[~2011-01-07 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 15:02 Tom Tromey [this message]
2011-01-07 15:19 ` 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=m3d3o8oiym.fsf@fleche.redhat.com \
--to=tromey@redhat.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