From: alex.bennee@linaro.org
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v6] Add .travis.yml metadata for CI
Date: Wed, 6 Nov 2013 10:43:36 +0000 [thread overview]
Message-ID: <1383734617-10516-1-git-send-email-alex.bennee@linaro.org> (raw)
From: Alex Bennée <alex@bennee.com>
Hi,
I think this patch is ready to be merged via trivial. While I was
testing it last night it caught yet another regression
(register_subpage: Assertion, since fixed) so I think it proves it's
worth with that alone.
Since v5
- Forced the python to 2.4 (our current baseline python)
Alex Bennée (1):
.travis.yml: basic compile and check recipes
.travis.yml | 71 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 71 insertions(+)
create mode 100644 .travis.yml
--
1.8.4.2
next reply other threads:[~2013-11-06 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 10:43 alex.bennee [this message]
2013-11-06 10:43 ` [Qemu-devel] [PATCH v6] .travis.yml: basic compile and check recipes alex.bennee
2013-11-06 12:37 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
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=1383734617-10516-1-git-send-email-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@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 NNTP newsgroup(s).