From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Sergio Durigan Junior <sergiodj@redhat.com>
Subject: [commit] [testsuite patch] Skip py-unwind.exp on x86_64 -m32
Date: Wed, 20 Jul 2016 14:19:00 -0000 [thread overview]
Message-ID: <20160720141932.GA16994@host1.jankratochvil.net> (raw)
In-Reply-To: <64a6e349-ccc1-977b-38b7-334bfbeeb28c@redhat.com>
On Wed, 20 Jul 2016 15:49:51 +0200, Pedro Alves wrote:
> Jan, please go ahead with your patch then.
Checked in:
72b5d09937fa2dac8ca7c801b9ddefe1b0176b6f
Thanks,
Jan
next prev parent reply other threads:[~2016-07-20 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 14:30 Jan Kratochvil
2016-07-18 10:04 ` Yao Qi
2016-07-18 11:34 ` Jan Kratochvil
2016-07-19 10:06 ` Yao Qi
2016-07-19 18:04 ` Pedro Alves
2016-07-20 11:20 ` Yao Qi
2016-07-20 13:49 ` Pedro Alves
2016-07-20 14:19 ` Jan Kratochvil [this message]
2016-07-19 19:30 ` Sergio Durigan Junior
2016-07-20 13:48 ` Pedro Alves
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=20160720141932.GA16994@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.com \
--cc=sergiodj@redhat.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).