From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org, Sasha Smundak <asmundak@google.com>
Subject: [commit] [testsuite patch] Fix new FAIL: py-frame.exp: test Frame.read_register(rip)
Date: Mon, 12 Jan 2015 10:05:00 -0000 [thread overview]
Message-ID: <20150112100518.GA30753@host2.jankratochvil.net> (raw)
In-Reply-To: <87mw5osrqi.fsf@codesourcery.com>
On Mon, 12 Jan 2015 02:38:29 +0100, Yao Qi wrote:
> Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> > OK this way?
>
> Yes, it is OK to me.
Checked in:
7e67715dd369f0a0caadaa5e528918dd65176e3b
Jan
prev parent reply other threads:[~2015-01-12 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 14:38 Jan Kratochvil
2015-01-11 13:58 ` Yao Qi
2015-01-11 14:51 ` Jan Kratochvil
2015-01-12 1:38 ` Yao Qi
2015-01-12 10:05 ` Jan Kratochvil [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=20150112100518.GA30753@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=asmundak@google.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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).