From: Doug Evans <dje@google.com>
To: Scott Goldman <scottjg@vmware.com>
Cc: Tom Tromey <tromey@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add support for `user-defined` python commands
Date: Thu, 19 May 2011 23:16:00 -0000 [thread overview]
Message-ID: <BANLkTi=0n4LbR-3kWYJ20O0E_ETxoOqprQ@mail.gmail.com> (raw)
In-Reply-To: <F78BCF638F95D74A99D036114107EDB5028F325A1C@EXCH-MBX-3.vmware.com>
On Thu, May 19, 2011 at 12:27 PM, Scott Goldman <scottjg@vmware.com> wrote:
> My understanding of the discussion is that Doug was suggesting that we might want to support custom categories as a follow-on change (I don't think it was an objection to this patch).
Correct.
No objection to the patch (or at least the concept :-) I didn't review
it with a fine tooth comb for checkinability).
prev parent reply other threads:[~2011-05-19 23:16 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
2011-05-19 23:16 ` Doug Evans [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='BANLkTi=0n4LbR-3kWYJ20O0E_ETxoOqprQ@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=scottjg@vmware.com \
--cc=tromey@redhat.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