qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PATCH 0/4] Current Travis queue
Date: Fri, 15 Apr 2016 16:56:57 +0100	[thread overview]
Message-ID: <1460735821-12775-1-git-send-email-alex.bennee@linaro.org> (raw)

Hi,

The only addition is Stefan's libnfs-dev patch which will increase our
coverage. However I would like to get some consensus about the
configure hack for build stems. It doesn't provide globbing but IMHO
stem support is good enough for the common build cases (and preferable
to massive --target-list definitions). Obviously it makes things for
travis neater but I hope it is useful to normal configure users as
well.

Alex Bennée (3):
  ./configure: accept stems to match a range of targets
  .travis.yml: reduce target list on core configure tweaks
  .travis.yml: add trusty GCE target

Stefan Hajnoczi (1):
  .travis.yml: add libnfs-dev for NFS block driver

 .travis.yml | 29 ++++++++++++++++++++---------
 configure   | 19 +++++++++++++++++--
 2 files changed, 37 insertions(+), 11 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-04-15 15:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 15:56 Alex Bennée [this message]
2016-04-15 15:56 ` [Qemu-devel] [PATCH 1/4] ./configure: accept stems to match a range of targets Alex Bennée
2016-04-15 15:56 ` [Qemu-devel] [PATCH 2/4] .travis.yml: reduce target list on core configure tweaks Alex Bennée
2016-04-15 16:07   ` Peter Maydell
2016-04-18  9:15     ` Alex Bennée
2016-04-18  9:17       ` Peter Maydell
2016-04-18  9:50         ` Alex Bennée
2016-04-15 15:57 ` [Qemu-devel] [PATCH 3/4] .travis.yml: add libnfs-dev for NFS block driver Alex Bennée
2016-04-15 15:57 ` [Qemu-devel] [PATCH 4/4] .travis.yml: add trusty GCE target Alex Bennée

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=1460735821-12775-1-git-send-email-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).