From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Qt 4 fixes
Date: Tue, 31 Jul 2012 12:08:18 +0100 [thread overview]
Message-ID: <1343732898.9526.3.camel@ted> (raw)
In-Reply-To: <cover.1343691019.git.paul.eggleton@linux.intel.com>
On Tue, 2012-07-31 at 00:30 +0100, Paul Eggleton wrote:
> The following changes since commit ab0187c13b2b0a041bf3d98c3a53bd3f45a624de:
>
> libxcb: Update for python-native changes (2012-07-30 16:53:49 +0100)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib paule/qt4-fixes-1
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/qt4-fixes-1
>
> Paul Eggleton (2):
> qt4: allow recipes building commercial edition
> qt4: make font packaging specific to embedded version
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-07-31 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 23:30 [PATCH 0/2] Qt 4 fixes Paul Eggleton
2012-07-30 23:31 ` [PATCH 1/2] qt4: allow recipes building commercial edition Paul Eggleton
2012-07-30 23:31 ` [PATCH 2/2] qt4: make font packaging specific to embedded version Paul Eggleton
2012-07-31 11:08 ` Richard Purdie [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=1343732898.9526.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.