From: Joel Brobecker <brobecker@adacore.com>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/4 v1] Add xmethod documentation and NEWS entry
Date: Tue, 03 Jun 2014 17:57:00 -0000 [thread overview]
Message-ID: <20140603175723.GA16336@adacore.com> (raw)
In-Reply-To: <CAGyQ6gz2g6UMBNcZprDcMhG-Ts4Fd3jy6Hu3HhQ7jA3CMQTCOA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
Hello!
> 2014-05-06 Siva Chandra Reddy <sivachandra@google.com>
> doc/
> * python.texi (Xmethods In Python, XMethod API)
> (Writing an Xmethod): New nodes.
> (Python API): New menu entries "Xmethods In Python",
> "Xmethod API", "Writing an Xmethod".
[...]
> +@defun register_xmethod_matcher(locus, matcher, replace=False)
> +The @code{matcher} is registered with @code{locus}, replacing an
> +existing matcher with the same name as @code{matcher} if
> +@code{replace} is @code{True}. @code{locus} can be a
> +@code{gdb.Objfile} object (@pxref{Objfiles In Python}), or a
> +@code{gdb.Progspace} object (@pxref{Program Spaces In Python}), or
^^^^^^^^^^^^^^^^^^^^^^^^
This reference was incorrect and caused the documentation build to fail.
I fixed it by pushing the attached commit.
gdb/doc/ChangeLog:
* python.texi (Xmethod API): Fix reference to "Progspaces In
Python".
Tested by rebuilding all documentation formats.
--
Joel
[-- Attachment #2: 0001-gdb-doc-python.texi-Fix-reference-to-Progspaces-In-P.patch --]
[-- Type: text/x-diff, Size: 1619 bytes --]
From 1e47491b33aac7447697c3cdeff0bbdbba5d58a0 Mon Sep 17 00:00:00 2001
From: Joel Brobecker <brobecker@adacore.com>
Date: Tue, 3 Jun 2014 10:39:03 -0700
Subject: [PATCH] gdb/doc/python.texi: Fix reference to "Progspaces In Python".
A recent change broke the documentation build due to a think-o
in a reference. Fixed thusly.
gdb/doc/ChangeLog:
* python.texi (Xmethod API): Fix reference to "Progspaces In
Python".
Tested by rebuilding all documentation formats.
---
gdb/doc/ChangeLog | 5 +++++
gdb/doc/python.texi | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 16a60f3..237c9a4 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2014-06-03 Joel Brobecker <brobecker@adacore.com>
+
+ * python.texi (Xmethod API): Fix reference to "Progspaces In
+ Python".
+
2014-06-03 Siva Chandra Reddy <sivachandra@google.com>
* python.texi (Xmethods In Python, XMethod API)
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index 1ba248b..2f1b71f 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -2322,7 +2322,7 @@ The @code{matcher} is registered with @code{locus}, replacing an
existing matcher with the same name as @code{matcher} if
@code{replace} is @code{True}. @code{locus} can be a
@code{gdb.Objfile} object (@pxref{Objfiles In Python}), or a
-@code{gdb.Progspace} object (@pxref{Program Spaces In Python}), or
+@code{gdb.Progspace} object (@pxref{Progspaces In Python}), or
@code{None}. If it is @code{None}, then @code{matcher} is registered
globally.
@end defun
--
1.9.1
prev parent reply other threads:[~2014-06-03 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 19:06 Siva Chandra
2014-06-02 19:17 ` Eli Zaretskii
2014-06-02 20:43 ` Siva Chandra
2014-06-03 6:57 ` Eli Zaretskii
2014-06-03 17:10 ` Siva Chandra
2014-06-03 17:57 ` Joel Brobecker [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=20140603175723.GA16336@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.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