All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	mjt@tls.msk.ru, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] configure: bump glib version to 2.16
Date: Tue, 10 Mar 2015 13:43:14 -0400	[thread overview]
Message-ID: <54FF2D32.2020508@redhat.com> (raw)
In-Reply-To: <CAFEAcA-qRPKMC3gZ-aO-oDOxULQsJ-cLGAsRC331+DPMki781g@mail.gmail.com>



On 03/10/2015 01:41 PM, Peter Maydell wrote:
>
>
> On 10 March 2015 at 17:37, John Snow <jsnow@redhat.com
> <mailto:jsnow@redhat.com>> wrote:
>
>     Our qtest suite relies on many functions available only in glib 2.16+.
>     Even though our base QEMU binary may only require 2.12+, it is confusing
>     to have two separate version requirements.
>
>     Thus, this is an attempt to re-establish a sane baseline for the entire
>     project at 2.16+.
>
>
>
> Why 2.16 rather than the 2.22 that we seem to have converged
> on in discussions on-list?
>
> -- PMM
>

Wasn't aware we were actually going through with that; it had looked 
like we were going to refrain from fiddling with it because we found a 
workaround that sufficed for glib 2.12.

2.16 is just the minimum that qtests currently actually requires.

If, however, we *are* going to shoot for 2.22, then NACK this and let's 
do that instead.

--js

  reply	other threads:[~2015-03-10 17:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 17:37 [Qemu-devel] [PATCH] configure: bump glib version to 2.16 John Snow
2015-03-10 17:40 ` John Snow
2015-03-10 17:41 ` Peter Maydell
2015-03-10 17:43   ` John Snow [this message]
2015-03-10 17:45     ` Peter Maydell
2015-05-07 12:22       ` Peter Maydell
2015-05-07 15:12         ` John Snow
2015-05-08  6:15           ` Markus Armbruster

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=54FF2D32.2020508@redhat.com \
    --to=jsnow@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --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.