From: Cristian Iorga <cristian.iorga@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] libpcap and libtirpc PUs
Date: Mon, 16 Dec 2013 19:02:45 +0200 [thread overview]
Message-ID: <cover.1387213322.git.cristian.iorga@intel.com> (raw)
The following changes since commit 9daa1de753e58b7f678e68cf307f6028c0c79a6a:
qemu/local.conf.sample: Add sdl PACKAGECONFIG (2013-12-16 12:13:59 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ciorga/PUs
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ciorga/PUs
Cristian Iorga (2):
libtirpc: upgrade to 0.2.4
libpcap: upgrade to 1.5.2
meta/recipes-connectivity/libpcap/libpcap/aclocal.patch | 8 ++++----
.../libpcap/{libpcap_1.4.0.bb => libpcap_1.5.2.bb} | 4 ++--
.../libtirpc-0.2.3/obsolete_automake_macros.patch | 15 ---------------
.../libtirpc-0.2.1-fortify.patch | 0
.../remove-des-uclibc.patch | 0
.../libtirpc/{libtirpc_0.2.3.bb => libtirpc_0.2.4.bb} | 8 +++++---
6 files changed, 11 insertions(+), 24 deletions(-)
rename meta/recipes-connectivity/libpcap/{libpcap_1.4.0.bb => libpcap_1.5.2.bb} (80%)
delete mode 100644 meta/recipes-extended/libtirpc/libtirpc-0.2.3/obsolete_automake_macros.patch
rename meta/recipes-extended/libtirpc/{libtirpc-0.2.3 => libtirpc-0.2.4}/libtirpc-0.2.1-fortify.patch (100%)
rename meta/recipes-extended/libtirpc/{libtirpc-0.2.3 => libtirpc-0.2.4}/remove-des-uclibc.patch (100%)
rename meta/recipes-extended/libtirpc/{libtirpc_0.2.3.bb => libtirpc_0.2.4.bb} (84%)
--
1.8.3.2
next reply other threads:[~2013-12-16 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 17:02 Cristian Iorga [this message]
2013-12-16 17:02 ` [PATCH 1/2] libtirpc: upgrade to 0.2.4 Cristian Iorga
2013-12-16 19:14 ` Saul Wold
2013-12-16 17:02 ` [PATCH 2/2] libpcap: upgrade to 1.5.2 Cristian Iorga
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.1387213322.git.cristian.iorga@intel.com \
--to=cristian.iorga@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.