From: Tom Tromey <tromey@redhat.com>
To: Scott Goldman <scottjg@vmware.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add support for `user-defined` python commands
Date: Thu, 19 May 2011 20:23:00 -0000 [thread overview]
Message-ID: <m3ei3u8mop.fsf@fleche.redhat.com> (raw)
In-Reply-To: <F78BCF638F95D74A99D036114107EDB5028F325A1C@EXCH-MBX-3.vmware.com> (Scott Goldman's message of "Thu, 19 May 2011 12:27:05 -0700")
Tom> This needs a doc review.
Scott> That's not a separate mailing list, is it?
Nope, it will happen here.
I will send you the paperwork stuff off-list.
Tom
next prev parent reply other threads:[~2011-05-19 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 23:28 Scott J. Goldman
2011-05-19 1:59 ` Doug Evans
2011-05-19 2:54 ` Scott Goldman
2011-05-19 3:08 ` Doug Evans
2011-05-19 16:44 ` Tom Tromey
2011-05-19 19:27 ` Scott Goldman
2011-05-19 20:23 ` Tom Tromey [this message]
2011-05-19 23:16 ` Doug Evans
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=m3ei3u8mop.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--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