From: "Eric Bénard" <eric@eukrea.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
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: Mon, 19 Sep 2011 21:33:30 +0200 [thread overview]
Message-ID: <4E77990A.5080504@eukrea.com> (raw)
In-Reply-To: <1316437421.14488.13.camel@ted>
Hi,
Le 19/09/2011 15:03, Richard Purdie a écrit :
> On Mon, 2011-09-19 at 09:25 -0300, Otavio Salvador wrote:
>> On Mon, Sep 19, 2011 at 09:09, Koen Kooi<koen@dominion.thruhere.net>
>> wrote: ...
>>> I'd like to see 4.7.4 go in. Richard and Saul have made it clear that
>>> removing 4.7.3 isn't going to happen before the release, so I'm trying
>>> make a compromise here. Are you saying you would find it unacceptable
>>> for both 4.7.3 and 4.7.4 to be in OE-core for a short while?
>>
>> Sure not. I can live with that and this is better then nothing but I
>> think Richard and Saul might rethink this assortment as 4.7.4 is in use
>> by us and proved stable too.
>
> The fact remains nobody has collected up the patches and presented Saul/I
> with a pull request collecting up these pieces. I've not even seen the
> patch addressing the regression posted, people just seem to agree one
> exists.
>
as said last weekend I'm working on such a patch collection (including the fix
for the regression).
I hope that to be ready tomorrow (tuesday 20) as I was afk since saturday.
Thanks,
Eric
next prev parent reply other threads:[~2011-09-19 20:57 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
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 [this message]
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=4E77990A.5080504@eukrea.com \
--to=eric@eukrea.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.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