From: Denys Dmytriyenko <denis@denix.org>
To: meta-arago@arago-project.org
Subject: [oe-layersetup][PATCH 2/2] arago-morty-config: add config to track morty branches
Date: Mon, 14 Nov 2016 18:34:31 -0500 [thread overview]
Message-ID: <1479166471-30960-2-git-send-email-denis@denix.org> (raw)
In-Reply-To: <1479166471-30960-1-git-send-email-denis@denix.org>
From: Denys Dmytriyenko <denys@ti.com>
meta-ti and meta-arago point to master for now, until remaining issues fixed
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
---
configs/arago-morty-config.txt | 12 ++++++++++++
1 file changed, 12 insertions(+)
create mode 100644 configs/arago-morty-config.txt
diff --git a/configs/arago-morty-config.txt b/configs/arago-morty-config.txt
new file mode 100644
index 0000000..ce7dbac
--- /dev/null
+++ b/configs/arago-morty-config.txt
@@ -0,0 +1,12 @@
+# This file takes repo entries in the format
+# repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern]
+
+bitbake,git://git.openembedded.org/bitbake,1.32,HEAD,layers=
+meta-arago,git://arago-project.org/git/meta-arago.git,master,HEAD,layers=meta-arago-distro:meta-arago-extras
+meta-qt5,git://github.com/meta-qt5/meta-qt5.git,morty,HEAD,layers=
+meta-openembedded,git://git.openembedded.org/meta-openembedded,morty,HEAD,layers=meta-networking:meta-ruby:meta-python:meta-oe
+meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD,layers=
+meta-linaro,git://git.linaro.org/openembedded/meta-linaro.git,morty,HEAD,layers=meta-linaro-toolchain:meta-optee
+oe-core,git://git.openembedded.org/openembedded-core,morty,HEAD,layers=meta
+OECORELAYERCONF=./sample-files/bblayers.conf.sample
+OECORELOCALCONF=./sample-files/local-arago64.conf.sample
--
2.7.4
prev parent reply other threads:[~2016-11-14 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 23:34 [oe-layersetup][PATCH 1/2] arago-krogoth-config: un-pin meta-qt5 as QWaylandIntegration got fixed Denys Dmytriyenko
2016-11-14 23:34 ` Denys Dmytriyenko [this message]
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=1479166471-30960-2-git-send-email-denis@denix.org \
--to=denis@denix.org \
--cc=meta-arago@arago-project.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.