From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: pmuldoon@redhat.com, Joel Brobecker <brobecker@adacore.com>
Subject: [commit/doco] Fix unmatched @end table in gdb.texinfo.
Date: Tue, 29 Jun 2010 04:36:00 -0000 [thread overview]
Message-ID: <1277786149-11066-1-git-send-email-brobecker@adacore.com> (raw)
The documentation was failing to build, causing the nightly source
snapshot to fail. This patch fixes the failuse, and I think that's
how things were supposed to be, based on how the other sections nearby
are written.
2010-06-29 Joel Brobecker <brobecker@adacore.com>
* gdb.texinfo (Threads In Python): Fix unmatched @end table.
Tested by rebuilding gdb.texinfo without error this time, and by visually
checking the result.
---
gdb/doc/ChangeLog | 4 ++++
gdb/doc/gdb.texinfo | 1 +
2 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 88ddc16..700ccfb 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2010-06-29 Joel Brobecker <brobecker@adacore.com>
+
+ * gdb.texinfo (Threads In Python): Fix unmatched @end table.
+
2010-06-28 Phil Muldoon <pmuldoon@redhat.com>
Tom Tromey <tromey@redhat.com>
Thiago Jung Bauermann <bauerman@br.ibm.com>
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index d09e79d..14b0092 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -21118,6 +21118,7 @@ does not use that identifier.
A @code{gdb.InferiorThread} object has the following methods:
+@table @code
@defmethod InferiorThread switch
This changes @value{GDBN}'s currently selected thread to the one represented
by this object.
--
1.7.1
next reply other threads:[~2010-06-29 4:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 4:36 Joel Brobecker [this message]
2010-06-29 17:36 ` Eli Zaretskii
2010-06-29 20:04 ` Phil Muldoon
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=1277786149-11066-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.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