From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Remove @code for python
Date: Wed, 22 Mar 2017 12:43:00 -0000 [thread overview]
Message-ID: <1490186626-13186-1-git-send-email-yao.qi@linaro.org> (raw)
In-Reply-To: <83mvcfx0za.fsf@gnu.org>
There's no reason to use @code for Python the name of a programming
language.
gdb/doc:
2017-03-22 Yao Qi <yao.qi@linaro.org>
* python.texi (Inferiors In Python): Remove @code from Python.
---
gdb/doc/ChangeLog | 4 ++++
gdb/doc/python.texi | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 8253cbe..5eb3a6c 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2017-03-22 Yao Qi <yao.qi@linaro.org>
+
+ * python.texi (Inferiors In Python): Remove @code from Python.
+
2017-03-21 Tim Wiederhake <tim.wiederhake@intel.com>
* python.texi (Recordings In Python): Document return type of
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index 1fb8b25..ce5810e 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -2760,7 +2760,7 @@ return an empty tuple.
Read @var{length} addressable memory units from the inferior, starting at
@var{address}. Returns a buffer object, which behaves much like an array
or a string. It can be modified and given to the
-@code{Inferior.write_memory} function. In @code{Python} 3, the return
+@code{Inferior.write_memory} function. In Python 3, the return
value is a @code{memoryview} object.
@end defun
--
1.9.1
next prev parent reply other threads:[~2017-03-22 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 14:36 Python 3 vs. @code{Python} 3 in python.texi Yao Qi
2017-03-20 18:22 ` Eli Zaretskii
2017-03-22 12:43 ` Yao Qi [this message]
2017-03-22 15:39 ` [PATCH] Remove @code for python 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=1490186626-13186-1-git-send-email-yao.qi@linaro.org \
--to=qiyaoltc@gmail.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