From: Pedro Alves <palves@redhat.com>
To: David Taylor <dtaylor@emc.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: ping
Date: Fri, 10 May 2013 11:38:00 -0000 [thread overview]
Message-ID: <518CDC17.2090107@redhat.com> (raw)
In-Reply-To: <18642.1368130153@usendtaylorx2l>
On 05/09/2013 09:09 PM, David Taylor wrote:
> Will someone please commit this patch?
I got this.
It'd be good to put this into 7.6 as well.
I guess I'll be the lucky one who champions the
"put 7.6.1 release notes in the wiki" process.
I've filed PR15455 (http://sourceware.org/bugzilla/show_bug.cgi?id=15455).
I though it'd be best to come up with a test that helps makes sure
QTro doesn't regress, so I wrote one. More after lunch. :-)
--
Pedro Alves
next prev parent reply other threads:[~2013-05-10 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 19:06 ping (was: [PATCH] Fix for QTro remote packet) David Taylor
2013-05-09 19:24 ` Pedro Alves
2013-05-09 20:09 ` David Taylor
2013-05-10 11:38 ` Pedro Alves [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-11 10:56 Ping Tom Tromey
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=518CDC17.2090107@redhat.com \
--to=palves@redhat.com \
--cc=dtaylor@emc.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