From: akuster808 <akuster808@gmail.com>
To: "MacDonald, Joe" <Joe_MacDonald@mentor.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 11:30:27 -0800 [thread overview]
Message-ID: <61ed17a3-a0d3-6bc1-c84b-e914ecfcc399@gmail.com> (raw)
In-Reply-To: <7e8d4f35-6212-46c1-84d3-a386aeae326d@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]
On 02/24/2018 10:26 AM, MacDonald, Joe wrote:
> Hey Armin,
>
> Your branch includes at least some (I haven't looked to see if it's
> all, seems likely) of the changes I have merged and ready to include
> for meta-networking. Since I haven't pushed them yet and wouldn't be
> before tonight at the earliest, do you want me to wait? Or were they
> just included in your tree for testing? I don't want to cause you
> unnecessary merge conflicts.
>
Yeah, After I sent it, I thought maybe I should have given the start and
end range.
"zsh: move to recipes-shells" to top "postgres: move to recipes-dbs"
- armin
> -J.
>
> On Feb 24, 2018 12:57 PM, akuster808 <akuster808@gmail.com> 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
>
> - armin
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
[-- Attachment #2: Type: text/html, Size: 4015 bytes --]
next prev parent reply other threads:[~2018-02-24 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 18:26 [RFC] meta-openembedded/meta-oe re-org MacDonald, Joe
2018-02-24 19:30 ` akuster808 [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-24 17:56 akuster808
2018-02-24 18:38 ` Tom Rini
2018-02-25 22:55 ` akuster808
[not found] ` <CADNbA1rnfQfQJ-78WFXdJHeZKGQXPnQ+hUY1zFi0SEDRiew4ig@mail.gmail.com>
2018-02-25 22:46 ` Derek Straka
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=61ed17a3-a0d3-6bc1-c84b-e914ecfcc399@gmail.com \
--to=akuster808@gmail.com \
--cc=Joe_MacDonald@mentor.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