From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] 2.4 tree reopened; post-mortem of 2.3
Date: Mon, 27 Apr 2015 20:46:42 +0200 [thread overview]
Message-ID: <553E8412.2050600@suse.de> (raw)
In-Reply-To: <CAFEAcA9WFRH6-mTsQ+bvy8OKCL0Q4WtUF_cuLgkYfSspBJ95Hg@mail.gmail.com>
Am 27.04.2015 um 19:04 schrieb Peter Maydell:
> (2) Late-breaking "this platform/compilation option combo is
> completely broken" issues
>
> Notably 32-bit PPC and ARM with latest libseccomp. Can we do
> anything to try to surface this sort of thing earlier in the
> release cycle, or is it just a fact of life that we have too many
> combinations to be able to get to testing them all in time?
All the features that I have enabled for 2.3 in our OBS now (including
libseccomp via a revert) will also be build-tested once I check in the
next -rc0 tarball. For now I don't package nightly Git versions though.
Cheers,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2015-04-27 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 17:04 [Qemu-devel] 2.4 tree reopened; post-mortem of 2.3 Peter Maydell
2015-04-27 18:46 ` Andreas Färber [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=553E8412.2050600@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=peter.maydell@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 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.