From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Fix meta-toolchain and meta-toolchain-gmae install problems
Date: Fri, 18 Jan 2013 17:13:36 -0600 [thread overview]
Message-ID: <cover.1358550581.git.mark.hatle@windriver.com> (raw)
The following changes since commit 18bc7b44ef58cbcbe32d45504d71eed54ef695a4:
guilt: add git 1.8.x support (2013-01-18 13:20:56 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib mhatle/ua-dep
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mhatle/ua-dep
Mark Hatle (2):
populate_sdk_rpm: Re-add a few system provides to the SDK
update-alternatives: Add a build-time dependency
meta/classes/populate_sdk_rpm.bbclass | 4 +++-
meta/classes/update-alternatives.bbclass | 13 +++++++++++++
meta/conf/distro/include/default-providers.inc | 2 +-
3 files changed, 17 insertions(+), 2 deletions(-)
next reply other threads:[~2013-01-18 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 23:13 Mark Hatle [this message]
2013-01-18 23:13 ` [PATCH 1/2] populate_sdk_rpm: Re-add a few system provides to the SDK Mark Hatle
2013-01-18 23:13 ` [PATCH 2/2] update-alternatives: Add a build-time dependency Mark Hatle
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.1358550581.git.mark.hatle@windriver.com \
--to=mark.hatle@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.