From: Siva Chandra <sivachandra@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 0/2] New 'explore' command
Date: Wed, 07 Mar 2012 18:47:00 -0000 [thread overview]
Message-ID: <CAGyQ6gw3biKm625Rk_+=kgfQ-2eb2xMH5-B6dpAfPQBL=bJQ2g@mail.gmail.com> (raw)
In-Reply-To: <20120307162409.GP2853@adacore.com>
OK. So it looks like we can ignore [patch 1/2] in this series then.
On Wed, Mar 7, 2012 at 9:54 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> Hi Siva,
>
> FWIW, I agree with Doug that a Python version of the command would be
> better suited...
>
> --
> Joel
prev parent reply other threads:[~2012-03-07 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 11:28 Siva Chandra
2012-03-07 16:24 ` Joel Brobecker
2012-03-07 18:47 ` Siva Chandra [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='CAGyQ6gw3biKm625Rk_+=kgfQ-2eb2xMH5-B6dpAfPQBL=bJQ2g@mail.gmail.com' \
--to=sivachandra@google.com \
--cc=brobecker@adacore.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