From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/4] Pin gvfs before making 1.7.2 default
Date: Sun, 20 Feb 2011 14:56:03 -0700 [thread overview]
Message-ID: <4D618DF3.50406@mentor.com> (raw)
In-Reply-To: <ijrber$3gb$1@dough.gmane.org>
On 02/20/2011 08:19 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 20-02-11 16:09, Tom Rini wrote:
>> With the recent change to add glib-2.28.0 and make it default,
>
> I'm still not sure that was the right decision, given the current
> fallout. Next time a new version gets added, it shouldn't be the default
> untill problems like this have been fixed.
Yes. I think moving forward we need to put glib-2.0 on the list of
things that needs care when adding new non-default versions since it's
used to widely (and I'll beg for the glib-mkenums patch to not be
dropped next time around, I can't build more than minimal-image and
meta-toolchain in my matrix without that bugfix).
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2011-02-20 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 15:09 [PATCH 0/4] Pin gvfs before making 1.7.2 default Tom Rini
2011-02-20 15:09 ` [PATCH 1/4] angstrom-2008: Pin gvfs at 1.6.6 Tom Rini
2011-02-20 15:20 ` Koen Kooi
2011-02-20 15:09 ` [PATCH 2/4] kaeilos 2009: Pin gvfs to 1.6.6 Tom Rini
2011-05-12 8:23 ` Marco Cavallini
2011-02-20 15:09 ` [PATCH 3/4] slugos: " Tom Rini
2011-02-22 1:22 ` Mike Westerhof
2011-02-20 15:09 ` [PATCH 4/4] gvfs 1.7.2: Drop DEFAULT_PREFERENCE Tom Rini
2011-02-20 15:19 ` [PATCH 0/4] Pin gvfs before making 1.7.2 default Koen Kooi
2011-02-20 21:56 ` Tom Rini [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=4D618DF3.50406@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.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