From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Fixes for diffutils and u-boot
Date: Mon, 5 Dec 2016 06:54:38 -0800 [thread overview]
Message-ID: <cover.1480949616.git.liezhi.yang@windriver.com> (raw)
The following changes since commit 11063a01d4511b2688ea7ba2d7359e4e07328c66:
ruby: upgrade to 2.3.1 (2016-11-30 15:47:17 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/2fixes
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/2fixes
Robert Yang (2):
diffutils: do_configure: fix "Argument list too long"
image.bbclass: inherit image_types_uboot when needed
meta/classes/image.bbclass | 9 +++++++++
meta/recipes-extended/diffutils/diffutils_3.4.bb | 3 +++
2 files changed, 12 insertions(+)
--
2.9.0
next reply other threads:[~2016-12-05 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 14:54 Robert Yang [this message]
2016-12-05 14:54 ` [PATCH 1/2] diffutils: do_configure: fix "Argument list too long" Robert Yang
2016-12-05 18:23 ` Khem Raj
2016-12-06 2:11 ` Robert Yang
2016-12-06 2:38 ` Khem Raj
2016-12-05 14:54 ` [PATCH 2/2] image.bbclass: inherit image_types_uboot when needed 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.1480949616.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox