qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Current Travis patches
Date: Wed, 9 Nov 2016 14:27:00 +0000	[thread overview]
Message-ID: <20161109142700.GG31111@stefanha-x1.localdomain> (raw)
In-Reply-To: <20161109121157.30815-1-alex.bennee@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 949 bytes --]

On Wed, Nov 09, 2016 at 12:11:55PM +0000, Alex Bennée wrote:
> Hi,
> 
> Not much here but since Daniel sped up the build by trimming out most
> of the clang mirrors of gcc I added one additional clang build which
> uses the current stable branch. Hopefully this still gives us enough
> coverage.
> 
> As this speeds up testing on merges and doesn't affect QEMU code
> itself I'll ask if we can merge this in the 2.8 cycle? If so I'll send
> a pull request in a few days assuming no objection to the patches
> themselves.
> 
> Alex Bennée (1):
>   travis: add Trusty with clang stable build
> 
> Daniel P. Berrange (1):
>   travis: trim out most clang builds
> 
>  .travis.yml | 24 +++++++++++++++++++++++-
>  1 file changed, 23 insertions(+), 1 deletion(-)

Despite .travis.yml not affecting the QEMU binary I want to stick to the
"bug fixes only" soft freeze policy for the 2.8 release.  Please queue
it for 2.9.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  parent reply	other threads:[~2016-11-09 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 12:11 [Qemu-devel] [PATCH 0/2] Current Travis patches Alex Bennée
2016-11-09 12:11 ` [Qemu-devel] [PATCH 1/2] travis: trim out most clang builds Alex Bennée
2016-11-09 12:11 ` [Qemu-devel] [PATCH 2/2] travis: add Trusty with clang stable build Alex Bennée
2016-11-09 14:27 ` Stefan Hajnoczi [this message]
2016-11-09 15:08   ` [Qemu-devel] [PATCH 0/2] Current Travis patches 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=20161109142700.GG31111@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=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).