From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Simon Marchi <simon.marchi@efficios.com>,
gdb-patches@sourceware.org, kevinb@redhat.com
Subject: Re: [PATCH] Small fix to gdb.Value constructor doc
Date: Tue, 05 Mar 2019 19:02:00 -0000 [thread overview]
Message-ID: <1005efd574da60ae6e3999bf214d083d@polymtl.ca> (raw)
In-Reply-To: <83sgw1cjt3.fsf@gnu.org>
On 2019-03-05 12:28, Eli Zaretskii wrote:
>> From: Simon Marchi <simon.marchi@efficios.com>
>> Cc: Kevin Buettner <kevinb@redhat.com>,
>> Eli Zaretskii <eliz@gnu.org>,
>> Simon Marchi <simon.marchi@efficios.com>
>> Date: Tue, 5 Mar 2019 12:05:44 -0500
>>
>> gdb/doc/ChangeLog:
>>
>> * python.texi (Values From Inferior): Change synopsys of the
>> second form of Value.__init__.
>
> Thanks, this is OK, but please take care of this gotcha:
>
>> -@defun Value.__init__ (@var{val}, @r{[}, type @r{]})
>> +@defun Value.__init__ (@var{val}, type)
>
> "type" should also be in @var.
I pushed it with this fixed.
Thanks,
Simon
prev parent reply other threads:[~2019-03-05 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 17:06 Simon Marchi
2019-03-05 18:52 ` Kevin Buettner
[not found] ` <83sgw1cjt3.fsf@gnu.org>
2019-03-05 19:02 ` Simon Marchi [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=1005efd574da60ae6e3999bf214d083d@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=simon.marchi@efficios.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