From: Martin Jansa <martin.jansa@gmail.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] meta/conf/layer.conf: Add recommended download layer
Date: Wed, 23 Nov 2016 19:10:39 +0100 [thread overview]
Message-ID: <20161123181039.GF3265@jama> (raw)
In-Reply-To: <20161123174209.211349-2-mark.hatle@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On Wed, Nov 23, 2016 at 11:42:09AM -0600, Mark Hatle wrote:
> This is a Wind River specific patch and not generally applicable.
Then why is it sent to oe-core ML?
>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
> meta/conf/layer.conf | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
> index 24b4df0..a94e524 100644
> --- a/meta/conf/layer.conf
> +++ b/meta/conf/layer.conf
> @@ -11,6 +11,8 @@ BBFILE_PRIORITY_core = "5"
> # cause compatibility issues with other layers
> LAYERVERSION_core = "9"
>
> +LAYERRECOMMENDS_core = "oe-core-dl-2-2"
> +
> BBLAYERS_LAYERINDEX_NAME_core = "openembedded-core"
>
> # Set a variable to get to the top of the metadata location
> --
> 2.9.3
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2016-11-23 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 17:42 [PATCH] Add recommended layer to oe-core Mark Hatle
2016-11-23 17:42 ` [PATCH] meta/conf/layer.conf: Add recommended download layer Mark Hatle
2016-11-23 18:10 ` Martin Jansa [this message]
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=20161123181039.GF3265@jama \
--to=martin.jansa@gmail.com \
--cc=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.