From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org,
yocto@yoctoproject.org
Subject: Please submit your unindexed layers
Date: Thu, 02 May 2013 14:27:58 +0100 [thread overview]
Message-ID: <2924564.6VWmlqGvL5@helios> (raw)
Hi all,
Even a cursory search of github reveals that there are a growing number of
layers being worked on in the community that aren't currently listed in the OE
layer index. I don't think it would be right for us to just add all of these
in bulk as we don't necessarily have all the needed information to do so, and
it's not clear if some of them are forks, or if they will continue to be
published in the same place, etc. So, what we really need is for the
maintainers of these layers to submit them to the layer index themselves, or
have someone else do it on their behalf.
If you're maintaining a publicly accessible layer that already does something
useful and is not currently in the OE layer index, please submit it so that
other folks in the community can find it easily. The submission form doesn't
need a login and is pretty straightforward to fill in:
http://layers.openembedded.org/layerindex/submit/
If you have any problems or concerns please let me know.
Thanks!
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2013-05-02 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 13:27 Paul Eggleton [this message]
2013-05-02 13:54 ` Please submit your unindexed layers Carlos Rafael Giani
2013-05-02 14:10 ` Paul Eggleton
[not found] ` <969F26A8BAB325438E7EB80D3C3134FB1622BB2A@IRSMSX102.ger.corp.intel.com>
2013-05-07 10:49 ` Carlos Rafael Giani
2013-05-07 13:53 ` Chris Larson
2013-05-07 14:03 ` Burton, Ross
2013-05-02 14:17 ` 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=2924564.6VWmlqGvL5@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=yocto@yoctoproject.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.