From: Philip Balister <philip@balister.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Should the devmem2 recipe move to oe-core?
Date: Sat, 28 Nov 2015 21:30:39 -0500 [thread overview]
Message-ID: <565A634F.4020508@balister.org> (raw)
I was poking at the layer index and ran across this:
http://layers.openembedded.org/layerindex/branch/master/recipes/?q=devmem
The recipe appears in 4 layers.
Should we just move it to openembedded-core? I wonder how easy it would
be to have the layer index report duplicate recipes?
Philip
next reply other threads:[~2015-11-29 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 2:30 Philip Balister [this message]
2015-11-30 7:09 ` Should the devmem2 recipe move to oe-core? Andre McCurdy
2015-11-30 14:26 ` Philip Balister
2015-12-02 19:44 ` Philip Balister
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=565A634F.4020508@balister.org \
--to=philip@balister.org \
--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.