From: Eli Zaretskii <eliz@gnu.org>
To: Scott Goldman <scottjg@vmware.com>
Cc: dje@google.com, pmuldoon@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow user-defined as a category for python gdb macros (resend)
Date: Thu, 23 Feb 2012 04:24:00 -0000 [thread overview]
Message-ID: <83d396tcsr.fsf@gnu.org> (raw)
In-Reply-To: <03E840D17E263A48A5766AD576E0423A03DAB7AED1@exch-mbx-111.vmware.com>
> From: Scott Goldman <scottjg@vmware.com>
> CC: Phil Muldoon <pmuldoon@redhat.com>, "eliz@gnu.org" <eliz@gnu.org>, "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> Date: Wed, 22 Feb 2012 19:02:20 -0800
>
> +List all user-defined commands and all python commands defined in class COMAND_USER. For user-defined commands, the first line of the documentation
> +(if any) is included. For python commands, the python docstring (if any) is included.
Two spaces between sentences, please. And please don't use such long
lines, they make the text harder to read.
OK with those changes.
Thanks.
next prev parent reply other threads:[~2012-02-23 4:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 0:49 Scott Goldman
2012-02-14 3:12 ` Doug Evans
2012-02-14 7:57 ` Scott Goldman
2012-02-14 18:09 ` Eli Zaretskii
2012-02-14 20:19 ` Doug Evans
2012-02-14 12:48 ` Phil Muldoon
2012-02-15 9:27 ` Scott Goldman
2012-02-16 14:23 ` Phil Muldoon
2012-02-16 17:16 ` Eli Zaretskii
2012-02-23 3:03 ` Doug Evans
2012-02-23 3:32 ` Scott Goldman
2012-02-23 4:24 ` Eli Zaretskii [this message]
2012-02-23 5:13 ` Scott Goldman
2012-02-23 6:03 ` Doug Evans
2012-02-23 6:56 ` Scott Goldman
2012-02-23 8:21 ` Scott Goldman
2012-02-24 23:49 ` Scott Goldman
2012-02-28 1:36 ` Doug Evans
2012-02-28 4:18 ` Scott Goldman
2012-02-28 7:51 ` Doug Evans
2012-02-29 0:45 ` [doc RFA] " Doug Evans
2012-02-29 4:17 ` Eli Zaretskii
2012-03-01 19:31 ` Doug Evans
2012-03-01 20:26 ` Keith Seitz
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=83d396tcsr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=scottjg@vmware.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