From: Tom Tromey <tom@tromey.com>
To: Richard Bunt <Richard.Bunt@arm.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH v2] gdbserver short-circuit-argument-list failures
Date: Thu, 14 Feb 2019 22:45:00 -0000 [thread overview]
Message-ID: <875ztm2dmz.fsf@tromey.com> (raw)
In-Reply-To: <f24a5b2a-8fb9-f656-db71-7373748d8efc@arm.com> (Richard Bunt's message of "Fri, 8 Feb 2019 11:10:21 +0000")
>>>>> "Richard" == Richard Bunt <Richard.Bunt@arm.com> writes:
Richard> Polite ping.
Thank you. This patch is ok.
Tom
prev parent reply other threads:[~2019-02-14 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 15:38 Richard Bunt
2019-02-08 11:10 ` Richard Bunt
2019-02-14 22:45 ` Tom Tromey [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=875ztm2dmz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Richard.Bunt@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).