From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH] gtk: prefer version 3.x
Date: Thu, 07 Jul 2016 16:27:30 +0200 [thread overview]
Message-ID: <1467901650.6647.7.camel@redhat.com> (raw)
In-Reply-To: <20160707092931.GH31666@redhat.com>
Hi,
> I'd further suggest that you might want to explicitly say that GTK-2.0
> support is deprecated, and set a date for its removal, as its days are
> clearly numbered, and it'd let us take advantage of more advanced GTK
> 3.0 features without piling on yet more #ifdefs.
Good idea.
> Perhaps print a warning in configure to say GTK-2.0 will be removed in
> the first release of 2018, if people use --with-gtkabi=2.0
I guess a warning is easily overlooked. New RfC patch follows in a
moment ...
cheers,
Gerd
prev parent reply other threads:[~2016-07-07 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 7:34 [Qemu-devel] [RfC PATCH] gtk: prefer version 3.x Gerd Hoffmann
2016-07-07 9:29 ` Daniel P. Berrange
2016-07-07 9:57 ` Peter Maydell
2016-07-07 14:27 ` Gerd Hoffmann [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=1467901650.6647.7.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--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 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).