From: "Eric Bénard" <eric@eukrea.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qt4: update to latest version 4.7.4
Date: Fri, 16 Sep 2011 14:22:21 +0200 [thread overview]
Message-ID: <4E733F7D.6090109@eukrea.com> (raw)
In-Reply-To: <201109161212.19780.paul.eggleton@linux.intel.com>
Hi,
Le 16/09/2011 13:12, Paul Eggleton a écrit :
> On Thursday 15 September 2011 21:06:22 Otavio Salvador wrote:
>> On Thu, Sep 15, 2011 at 15:41, Eric Bénard<eric@eukrea.com> wrote:
>> ...
>>
>>> Btw, this patch is only a minor update of qt so this would be interesting
>>> to have it into the 1.1 release imho.
>>
>> I agree with Eric that this is important to have into the release; rc
>> is OK to skip it but for final seems good to have it in.
>
> Considering there is at least one reported regression in 4.7.4, I'm not sure
> it would be a good idea to rush into it right now:
>
> https://bugreports.qt.nokia.com/browse/QTBUG-20925
>
We could also say that qt 4.7.4 fix many qt 4.7.3 bugs and integrate the patch
fixing this one and in the end get an improvement.
I don't understand why oe-core's development has to be stopped by yocto's
releases process but I may not have found the right page on the wiki
explaining all the details : may you please give me some links concerning this
policy ?
Maybe yocto could consider oe-core as an incubator instead of a follower else
I don't really see why we need to have the same project managed by the same
peoples with 2 different names.
Eric
next prev parent reply other threads:[~2011-09-16 12:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 20:07 [PATCH 1/2] qt4: add blacklist-diginotar-certs patch Eric Bénard
2011-09-10 20:07 ` [PATCH 2/2] qt4: update to latest version 4.7.4 Eric Bénard
2011-09-11 17:22 ` Anders Darander
2011-09-11 17:33 ` [PATCH] " Eric Bénard
2011-09-12 10:34 ` Paul Eggleton
2011-09-14 11:11 ` Koen Kooi
2011-09-14 13:09 ` Eric Bénard
2011-09-14 15:34 ` Otavio Salvador
2011-09-15 7:57 ` Eric Bénard
2011-09-15 15:07 ` Otavio Salvador
2011-09-14 17:03 ` Koen Kooi
2011-09-15 17:32 ` Saul Wold
2011-09-15 18:41 ` Eric Bénard
2011-09-15 20:06 ` Otavio Salvador
2011-09-16 11:12 ` Paul Eggleton
2011-09-16 12:22 ` Eric Bénard [this message]
2011-09-16 12:54 ` Phil Blundell
2011-09-16 16:46 ` Richard Purdie
2011-09-16 13:11 ` Otavio Salvador
2011-09-19 9:45 ` Koen Kooi
2011-09-19 11:48 ` Otavio Salvador
2011-09-19 12:09 ` Koen Kooi
2011-09-19 12:25 ` Otavio Salvador
2011-09-19 13:03 ` Richard Purdie
2011-09-19 19:33 ` Eric Bénard
2011-09-20 21:18 ` Eric Bénard
2011-09-21 10:44 ` Koen Kooi
2011-09-21 12:52 ` Eric Bénard
2011-09-21 13:05 ` Koen Kooi
2011-09-21 13:16 ` Eric Bénard
2011-09-28 10:11 ` Paul Eggleton
2011-09-28 10:23 ` Eric Bénard
2011-09-28 13:11 ` Otavio Salvador
2011-09-28 13:33 ` Richard Purdie
2011-09-30 11:47 ` Eric Bénard
2011-09-30 16:23 ` Paul Eggleton
2011-09-12 10:34 ` [PATCH 1/2] qt4: add blacklist-diginotar-certs patch Paul Eggleton
2011-09-15 17:34 ` Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2011-09-15 8:40 [PATCH] qt4: update to latest version 4.7.4 Eric Bénard
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=4E733F7D.6090109@eukrea.com \
--to=eric@eukrea.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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