From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>
Subject: Re: [RFC] "New" command "!"
Date: Tue, 08 Nov 2011 15:51:00 -0000 [thread overview]
Message-ID: <201111081550.45417.pedro@codesourcery.com> (raw)
In-Reply-To: <20111108093759.279E3246194@ruffy.mtv.corp.google.com>
On Tuesday 08 November 2011 09:37:58, Doug Evans wrote:
> Hi.
> I mentioned this before in an offhand comment,
> but now I'm submitting this RFC.
> I'll add tests,docs,NEWS if the code part is ok.
>
> Am I missing something?
> Is there a reason not to add this?
Looks good to me too.
--
Pedro Alves
next prev parent reply other threads:[~2011-11-08 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 9:38 Doug Evans
2011-11-08 14:56 ` Tom Tromey
2011-11-08 15:36 ` Hui Zhu
2011-11-08 15:44 ` Tom Tromey
2011-11-08 15:51 ` Pedro Alves [this message]
2011-11-08 17:26 ` Doug Evans
2011-11-11 17:19 ` [doc RFA] " Doug Evans
2011-11-11 19:31 ` Eli Zaretskii
2011-11-15 17:00 ` 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=201111081550.45417.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.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