From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Patches for guile and bind
Date: Tue, 22 Dec 2015 09:04:52 +0800 [thread overview]
Message-ID: <cover.1450746244.git.kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
The following changes since commit 5f406915b5e26761faa4ea5e0edd887ac5ae6e2f:
bitbake: toaster: remove 2 confusing parameters (2015-12-18 13:51:54 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib kangkai/misc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/misc
Kai Kang (2):
guile: remove redundant replacement of .pc file
bind: 9.10.2-P4 -> 9.10.3-P2
.../0001-build-use-pkg-config-to-find-libxml2.patch | 20 ++++++++++++++------
.../bind/{bind_9.10.2-P4.bb => bind_9.10.3-P2.bb} | 9 ++++++---
meta/recipes-devtools/guile/guile_2.0.11.bb | 19 ++++---------------
3 files changed, 24 insertions(+), 24 deletions(-)
rename meta/recipes-connectivity/bind/{bind_9.10.2-P4.bb => bind_9.10.3-P2.bb} (90%)
--
2.6.1
next reply other threads:[~2015-12-22 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 1:04 kai.kang [this message]
2015-12-22 1:04 ` [PATCH 1/2] guile: remove redundant replacement of .pc file kai.kang
2015-12-22 1:04 ` [PATCH 2/2] bind: 9.10.2-P4 -> 9.10.3-P2 kai.kang
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.1450746244.git.kai.kang@windriver.com \
--to=kai.kang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox