From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Upgrade chrpath and libevent
Date: Fri, 23 Dec 2011 09:31:15 -0800 [thread overview]
Message-ID: <cover.1324661415.git.scott.a.garman@intel.com> (raw)
Hello,
This pull request upgrades the chrpath and libevent recipes. It has
been build-tested on all 5 of our qemu architectures.
Scott
The following changes since commit c38693f78c968ab5f4bb557c20d1c8c55393ed6b:
opkg: Fix installation order in feeds with mutiple providers of packages (2011-12-22 22:38:09 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib sgarman/recipe-upgrades-final
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/recipe-upgrades-final
Scott Garman (2):
chrpath: upgrade to 0.14
libevent: upgrade to 2.0.16
meta/recipes-devtools/chrpath/chrpath_0.13.bb | 23 ---------------------
meta/recipes-devtools/chrpath/chrpath_0.14.bb | 23 +++++++++++++++++++++
meta/recipes-support/libevent/libevent_1.4.14b.bb | 19 -----------------
meta/recipes-support/libevent/libevent_2.0.16.bb | 22 ++++++++++++++++++++
4 files changed, 45 insertions(+), 42 deletions(-)
delete mode 100644 meta/recipes-devtools/chrpath/chrpath_0.13.bb
create mode 100644 meta/recipes-devtools/chrpath/chrpath_0.14.bb
delete mode 100644 meta/recipes-support/libevent/libevent_1.4.14b.bb
create mode 100644 meta/recipes-support/libevent/libevent_2.0.16.bb
--
1.7.5.4
next reply other threads:[~2011-12-23 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 17:31 Scott Garman [this message]
2011-12-23 17:31 ` [PATCH 1/2] chrpath: upgrade to 0.14 Scott Garman
2011-12-23 17:31 ` [PATCH 2/2] libevent: upgrade to 2.0.16 Scott Garman
2011-12-23 17:42 ` [PATCH 0/2] Upgrade chrpath and libevent Scott Garman
2011-12-26 21:12 ` Scott Garman
2011-12-28 18:37 ` Saul Wold
2011-12-29 15:05 ` Scott Garman
2011-12-29 15:28 ` Paul Eggleton
2011-12-29 20:42 ` Scott Garman
2011-12-29 22:06 ` Paul Eggleton
2012-01-04 0:02 ` 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=cover.1324661415.git.scott.a.garman@intel.com \
--to=scott.a.garman@intel.com \
--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.