From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"QEMU Trivial" <qemu-trivial@nongnu.org>,
"Fam Zheng" <famz@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1] configure: require glib-2.24
Date: Thu, 26 Apr 2018 13:10:02 +0100 [thread overview]
Message-ID: <20180426121002.GG26812@redhat.com> (raw)
In-Reply-To: <20180426140807.4a4a577b.olaf@aepfle.de>
On Thu, Apr 26, 2018 at 02:08:07PM +0200, Olaf Hering wrote:
> Am Thu, 26 Apr 2018 13:52:04 +0200
> schrieb Paolo Bonzini <pbonzini@redhat.com>:
>
> > min-glib Dockerfile is using glib 2.22
>
> Why did it not prevent the bad commit from entering 2.12?
Presumably the min-glib docker job didn't enable the vfio feature, which
is what contained the bad code.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-04-26 12:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 12:38 [Qemu-devel] [PATCH v1] configure: require glib-2.24 Olaf Hering
2018-04-18 12:45 ` Cornelia Huck
2018-04-18 12:55 ` Daniel P. Berrangé
2018-04-18 14:41 ` Cornelia Huck
2018-04-18 14:43 ` Daniel P. Berrangé
2018-04-19 7:19 ` Markus Armbruster
2018-04-19 7:30 ` Olaf Hering
2018-04-19 7:59 ` Daniel P. Berrangé
2018-04-19 8:54 ` Peter Maydell
2018-04-19 9:01 ` [Qemu-devel] [Qemu-trivial] " Kamil Rytarowski
2018-04-19 9:20 ` [Qemu-devel] " Gerd Hoffmann
2018-04-19 9:23 ` Daniel P. Berrangé
2018-04-18 14:45 ` Olaf Hering
2018-04-18 12:47 ` Daniel P. Berrangé
2018-04-18 13:00 ` Olaf Hering
2018-04-18 13:29 ` Peter Maydell
2018-04-18 14:44 ` Daniel P. Berrangé
2018-04-26 8:17 ` Peter Maydell
2018-04-26 9:19 ` Thomas Huth
2018-04-26 9:54 ` Peter Maydell
2018-04-26 11:52 ` Paolo Bonzini
2018-04-26 12:08 ` Olaf Hering
2018-04-26 12:10 ` Daniel P. Berrangé [this message]
2018-04-26 12:11 ` Olaf Hering
2018-04-26 12:39 ` Paolo Bonzini
2018-04-26 12:42 ` Paolo Bonzini
2018-04-26 12:42 ` Olaf Hering
2018-04-26 12:12 ` Peter Maydell
2018-04-18 13:34 ` Eric Blake
2018-04-18 12:53 ` no-reply
2018-04-18 13:04 ` Olaf Hering
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=20180426121002.GG26812@redhat.com \
--to=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=kraxel@redhat.com \
--cc=olaf@aepfle.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).