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>,
	Michael Tokarev <mjt@tls.msk.ru>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] configure: bump glib version to 2.16
Date: Thu, 07 May 2015 11:12:29 -0400	[thread overview]
Message-ID: <554B80DD.4000805@redhat.com> (raw)
In-Reply-To: <CAFEAcA_aUA=3BrdGH2=hfM+mJz+CWDpYDFx7m6GL+MjZqUBUnA@mail.gmail.com>



On 05/07/2015 08:22 AM, Peter Maydell wrote:
> On 10 March 2015 at 17:45, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 10 March 2015 at 17:43, John Snow <jsnow@redhat.com> wrote:
>>> 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.
>>
>> Well, we're not doing anything before QEMU 2.3 is released.
>> But if we bump the version requirement at all, then we might
>> as well move it to 2.22, because once you drop the "support RHEL5"
>> requirement then that's the newest version we can shift to without
>> breaking compilation on some other distro we care about (SUSE, in
>> this case).
> 
> So do people still want to bump the minimum glib version?
> If we're going to do it for 2.4 I would prefer to see the
> configure patch reasonably early in the release cycle I think.
> 
> -- PMM
> 

I think we determined that the minimum version could be as high as 2.22.

https://lists.gnu.org/archive/html/qemu-devel/2015-03/msg00488.html

  reply	other threads:[~2015-05-07 15:12 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
2015-03-10 17:45     ` Peter Maydell
2015-05-07 12:22       ` Peter Maydell
2015-05-07 15:12         ` John Snow [this message]
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=554B80DD.4000805@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.