From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/3] meta: 3 fixes
Date: Sat, 3 Jan 2015 06:39:19 -0800 [thread overview]
Message-ID: <cover.1420295873.git.liezhi.yang@windriver.com> (raw)
Hello,
For the first patch:
cpan-base.bbclass: avoid using immmediate assignment for PERLLIBDIRS
I'm not sure what changes recently cause I meet the error, does anyone
have any idea, please ?
// Robert
The following changes since commit 24f19fedb40d0af84beb8e9a6595ea06f09d4615:
gstreamer1.0-omx: use mulitple SCMs to fetch submodules (2014-12-31 08:22:53 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/3fixes
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rtb/3fixes
Robert Yang (3):
cpan-base.bbclass: avoid using immmediate assignment for PERLLIBDIRS
cups: check avahi before use it
cogl: enable egl-x11 when build with x11
meta/classes/cpan-base.bbclass | 4 +--
meta/recipes-extended/cups/cups.inc | 1 +
...1-test-ippserver.c-check-avahi-before-use.patch | 34 ++++++++++++++++++++
meta/recipes-graphics/cogl/cogl-1.0.inc | 6 ++--
4 files changed, 41 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-extended/cups/cups/0001-test-ippserver.c-check-avahi-before-use.patch
--
1.7.9.5
next reply other threads:[~2015-01-03 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 14:39 Robert Yang [this message]
2015-01-03 14:39 ` [PATCH 1/3] cpan-base.bbclass: avoid using immmediate assignment for PERLLIBDIRS Robert Yang
2015-01-03 14:39 ` [PATCH 2/3] cups: check avahi before use it Robert Yang
2015-01-03 14:39 ` [PATCH 3/3] cogl: enable egl-x11 when build with x11 Robert Yang
-- strict thread matches above, loose matches on Subject: below --
2015-02-03 1:22 [PATCH 0/3] meta: 3 fixes Robert Yang
2015-04-01 7:52 Robert Yang
2015-07-13 10:02 Robert Yang
2015-09-16 7:52 Robert Yang
2016-01-07 7:45 Robert Yang
2016-01-28 9:46 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.1420295873.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.