All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Current Travis patches
Date: Wed, 09 Nov 2016 15:08:41 +0000	[thread overview]
Message-ID: <87mvh88zd2.fsf@linaro.org> (raw)
In-Reply-To: <20161109142700.GG31111@stefanha-x1.localdomain>


Stefan Hajnoczi <stefanha@redhat.com> writes:

> 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.

Fair enough, I shall hold on to them for now.

>
> Stefan


--
Alex Bennée

      reply	other threads:[~2016-11-09 15:08 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 ` [Qemu-devel] [PATCH 0/2] Current Travis patches Stefan Hajnoczi
2016-11-09 15:08   ` Alex Bennée [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=87mvh88zd2.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.