Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Eric Bénard" <eric@eukrea.com>,
	"Paul Eggleton" <paul.eggleton@linux.intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: QT4 patches
Date: Fri, 16 Sep 2011 18:13:07 +0100	[thread overview]
Message-ID: <1316193195.20858.55.camel@ted> (raw)

Hi Paul/Eric,

I was trying to figure out where we're at with the QT4 patches. With
regard to the version update, I've seen talk of the first version of the
update being broken, a second version posted and then some talk of some
fix needed on top of that which I could find a patch for.

On top of this I think there is an SDK fix needed (I've replied with a
question about that).

There is also a qt4 demo split patch that looks like its been through a
couple of iterations and also some armv6 patch with feedback that there
are futher issues so I'm not sure what the status is there.

Firstly, I love the patches, its great to see these issues getting
sorted out. I am however getting very confused between all the patches
and their versions and its taken me a while to figure out what I'm
likely being expected to merge.

Could someone therefore please put together a combined pull request for
these pieces from a git branch? I will take them into master (assuming
some details get ironed out) but I'm not sure they can make the release
branch at this point (the fun with the .bbappend files isn't helping my
confidence there).

Cheers,

Richard







             reply	other threads:[~2011-09-16 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 17:13 Richard Purdie [this message]
2011-09-16 20:00 ` QT4 patches 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=1316193195.20858.55.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=eric@eukrea.com \
    --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