From: Phil Muldoon <pmuldoon@redhat.com>
To: <Paul_Koning@Dell.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: Doc: make python function/method descriptions look as in Python
Date: Tue, 06 Sep 2011 19:39:00 -0000 [thread overview]
Message-ID: <m3liu14g5t.fsf@redhat.com> (raw)
In-Reply-To: <09787EF419216C41A903FD14EE5506DD01534916A6@AUSX7MCPC103.AMER.DELL.COM> (Paul Koning's message of "Tue, 6 Sep 2011 10:37:30 -0500")
<Paul_Koning@Dell.com> writes:
> Here is an updated version. This one replaces defmethod by defun and defivar by defvar, with the class name explicit on the symbol as is the Python documentation convention. I'm sending the diff as an attachment, hope that works right.
I think it is great. If Eli is fine with it, and it meets the standards
of the GDB manual, I think it would be an improvement.
Cheers
Phil
next prev parent reply other threads:[~2011-09-06 19:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 21:23 Paul_Koning
2011-09-02 12:26 ` Pedro Alves
2011-09-02 16:45 ` Paul_Koning
2011-09-02 17:08 ` Pedro Alves
2011-09-03 19:46 ` Eli Zaretskii
2011-09-03 21:53 ` Matt Rice
2011-09-04 8:38 ` Paul_Koning
2011-09-04 10:37 ` Eli Zaretskii
2011-09-06 15:42 ` Paul_Koning
[not found] ` <09787EF419216C41A903FD14EE5506DD01534916B2@AUSX7MCPC103.AMER.DELL.COM>
2011-09-06 18:01 ` Paul Koning
2011-09-09 21:15 ` Paul Koning
2011-09-09 21:33 ` Eli Zaretskii
2011-09-15 17:19 ` Paul_Koning
2011-10-21 14:17 ` Kevin Pouget
2011-10-21 15:51 ` Tom Tromey
2011-09-06 19:39 ` Phil Muldoon [this message]
2011-09-06 19:45 ` Paul_Koning
2011-09-06 19:57 ` Paul_Koning
2011-09-06 20:07 ` Eli Zaretskii
2011-09-06 20:25 ` Paul_Koning
2011-09-07 0:45 ` Eli Zaretskii
2011-09-06 19:56 ` Eli Zaretskii
2011-09-06 20:01 ` Paul_Koning
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=m3liu14g5t.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=Paul_Koning@Dell.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