From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] Add recommended layer to oe-core
Date: Wed, 23 Nov 2016 11:42:08 -0600 [thread overview]
Message-ID: <20161123174209.211349-1-mark.hatle@windriver.com> (raw)
This patch is being sent for Yocto Project compliance reasons. It is not
expected to be integrated.
The patch is unique to Wind River Linux's implementation. We have
special layers called 'download layers', where we aggregate all of the
download content needed by a given layer. The layer recommends allows us to
optionally depend on these special layers.
Mark Hatle (1):
meta/conf/layer.conf: Add recommended download layer
meta/conf/layer.conf | 2 ++
1 file changed, 2 insertions(+)
--
2.9.3
next reply other threads:[~2016-11-23 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 17:42 Mark Hatle [this message]
2016-11-23 17:42 ` [PATCH] meta/conf/layer.conf: Add recommended download layer Mark Hatle
2016-11-23 18:10 ` Martin Jansa
2016-11-23 18:38 ` Mark Hatle
2016-11-23 18:56 ` Martin Jansa
2016-11-23 19:42 ` Mark Hatle
2016-11-24 1:16 ` Christopher Larson
2016-11-24 3:00 ` Mark Hatle
2016-11-24 11:13 ` Patrick Ohly
2016-11-24 14:03 ` Philip Balister
2016-11-24 16:14 ` Burton, Ross
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=20161123174209.211349-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox