From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH 0/2] A couple of fixes
Date: Mon, 19 Mar 2012 09:21:20 -0700 [thread overview]
Message-ID: <4F675D00.5050808@linux.intel.com> (raw)
In-Reply-To: <cover.1331821447.git.paul.eggleton@linux.intel.com>
On 03/15/2012 07:24 AM, Paul Eggleton wrote:
> The following changes since commit b055075ba5b9ff5250bc66be1cd8b222bdb86161:
>
> slang: Fix rpath QA warnings (2012-03-15 00:07:43 +0000)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib paule/fixes15
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/fixes15
>
> Paul Eggleton (2):
> util-linux: restore zlib and ncurses dependencies for native
> python-imaging: bring in fixes from meta-oe
>
> meta/recipes-core/util-linux/util-linux.inc | 2 +-
> meta/recipes-core/util-linux/util-linux_2.21.bb | 2 +-
> ...ng-setup.py-force-paths-for-zlib-freetyp.patch} | 36 +++++++++++++++----
> .../python/python-imaging_1.1.7.bb | 9 +++--
> 4 files changed, 36 insertions(+), 13 deletions(-)
> rename meta/recipes-devtools/python/python-imaging/{path.patch => 0001-python-imaging-setup.py-force-paths-for-zlib-freetyp.patch} (47%)
>
Merged into OE-Core
Thanks
Sau!
next prev parent reply other threads:[~2012-03-19 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 14:24 [PATCH 0/2] A couple of fixes Paul Eggleton
2012-03-15 14:24 ` [PATCH 1/2] util-linux: restore zlib and ncurses dependencies for native Paul Eggleton
2012-03-15 14:24 ` [PATCH 2/2] python-imaging: bring in fixes from meta-oe Paul Eggleton
2012-03-19 16:21 ` Saul Wold [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-24 18:59 [PATCH 0/2] A couple of fixes Saul Wold
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=4F675D00.5050808@linux.intel.com \
--to=sgw@linux.intel.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