Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: akuster808 <akuster808@gmail.com>
Cc: OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] meta-openembedded/meta-oe re-org
Date: Sat, 24 Feb 2018 13:38:11 -0500	[thread overview]
Message-ID: <20180224183811.GL4311@bill-the-cat> (raw)
In-Reply-To: <966e95a6-4401-5c12-b69c-9bd37bb236fd@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

On Sat, Feb 24, 2018 at 09:56:42AM -0800, akuster808 wrote:

> Hello,
> 
> I am planning on moving some recipes to new locations that are more
> in-line with their function.
> 
> Also, I plan on adding *-shells, *-dbs, *-security and *.crypto and
> moving the appropriate recipes there.
> 
> This might help facilitate folks signing up to maintain a grouping like
> recipes-crypto if that is their thing.
> 
> 
> I will be sending out patches later today for review.
> 
> I have staged the changes @
> http://cgit.openembedded.org/meta-openembedded-contrib/log/?h=akuster/meta-oe-reorg

Should some stuff perhaps be moved out to other layers?  More
specifically, should at least tomoyo-tools get moved to meta-security
with the rest of the tomoyo stuff?  I have less strong opinions on
leveldb (but maybe recipes-dbs instead) and passwdqc.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2018-02-24 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24 17:56 [RFC] meta-openembedded/meta-oe re-org akuster808
2018-02-24 18:38 ` Tom Rini [this message]
2018-02-25 22:55   ` akuster808
     [not found] ` <CADNbA1rnfQfQJ-78WFXdJHeZKGQXPnQ+hUY1zFi0SEDRiew4ig@mail.gmail.com>
2018-02-25 22:46   ` Derek Straka
  -- strict thread matches above, loose matches on Subject: below --
2018-02-24 18:26 MacDonald, Joe
2018-02-24 19:30 ` akuster808

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=20180224183811.GL4311@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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