From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/4] fix for guile and neard
Date: Fri, 16 Jan 2015 16:31:14 -0800 [thread overview]
Message-ID: <cover.1421454635.git.liezhi.yang@windriver.com> (raw)
The following changes since commit 6541799c2e9a5a1586676c207d62f885c70e24dc:
lib/oe/rootfs.py: Fix reference to abiversion file location (2015-01-16 23:14:26 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/neard_guile
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/neard_guile
Robert Yang (4):
Revert "guile: fixed installed-vs-shipped error"
guile: fix installed-vs-shipped error
neard: fix B != S
neard: fix parallel issue
meta/recipes-connectivity/neard/neard.inc | 4 +--
.../neard/Makefile.am-fix-parallel-issue.patch | 33 ++++++++++++++++++++
meta/recipes-connectivity/neard/neard_0.14.bb | 2 ++
...pends.patch => libguile-Makefile.am-hook.patch} | 23 ++++++++------
meta/recipes-devtools/guile/guile_2.0.11.bb | 2 +-
5 files changed, 51 insertions(+), 13 deletions(-)
create mode 100644 meta/recipes-connectivity/neard/neard/Makefile.am-fix-parallel-issue.patch
rename meta/recipes-devtools/guile/files/{libguile-Makefile.am-depends.patch => libguile-Makefile.am-hook.patch} (56%)
--
1.7.9.5
next reply other threads:[~2015-01-17 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 0:31 Robert Yang [this message]
2015-01-17 0:31 ` [PATCH 1/4] Revert "guile: fixed installed-vs-shipped error" Robert Yang
2015-01-17 0:31 ` [PATCH 2/4] guile: fix installed-vs-shipped error Robert Yang
2015-01-17 0:31 ` [PATCH 3/4] neard: fix B != S Robert Yang
2015-01-17 0:31 ` [PATCH 4/4] neard: fix parallel issue Robert Yang
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.1421454635.git.liezhi.yang@windriver.com \
--to=liezhi.yang@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 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.