From: Dave Cobbley <david.j.cobbley@linux.intel.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: openbmc@lists.ozlabs.org, prashanth.giri@dell.com,
sachit_bakshi@dell.com
Subject: Re: Managing openbmc with subtree
Date: Thu, 9 Aug 2018 17:31:32 -0700 [thread overview]
Message-ID: <fe79284e-e3d6-a71f-f055-6bcbe899fbd5@linux.intel.com> (raw)
In-Reply-To: <d20b9c39-38b1-dd91-4847-1a65479c0f51@linux.intel.com>
>> So to net these all out:
>>
>> *poky/
>>
>> *meta-openembedded/
>> *meta-virtualization/
>> *meta-security/
>> *meta-arm/
>> *meta-openpower/
>> *meta-x86/
>> *meta-phosphor/
>>
>> *meta-aspeed/
>> *meta-nuvoton/
>> *meta-raspberrypi/
>>
>> *meta-intel/
>> *meta-mellanox/
>> *meta-portwell/
>> *meta-quanta/
>> *meta-ibm/
>> *meta-ingrasys/
>> *meta-inventec/
>> *meta-rackspace/
>> *meta-qualcomm/
> Just to clarify - *meta-intel would contain our machine specific
> configurations for particular intel platforms, while *meta-x86 would
> contain image-like things that are generic to all x86 server platforms?
> Not sure I understand why meta-x86 exists if
> meta-intel/mellanox/portwell/quanta are all on the top level. Meta-x86
> was simply a folder in my proposal.
Looking at this further, I believe I understand the difference:
meta-intel is our actual baseboard products
meta-x86 is all things that relate specifically to baseboards that
contain x86 processors.
Does that sound right?
> -Dave
next prev parent reply other threads:[~2018-08-10 0:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 20:08 Managing openbmc with subtree Dave Cobbley
2018-07-20 17:42 ` Dave Cobbley
2018-07-20 17:43 ` Brad Bishop
2018-07-20 17:47 ` Brad Bishop
2018-08-01 21:53 ` Dave Cobbley
2018-08-06 17:30 ` Ed Tanous
2018-08-06 18:47 ` Brad Bishop
2018-08-07 17:16 ` Dave Cobbley
2018-08-07 19:30 ` Brad Bishop
2018-08-08 22:14 ` Dave Cobbley
2018-08-09 20:16 ` Brad Bishop
2018-08-09 22:23 ` Dave Cobbley
2018-08-10 0:31 ` Dave Cobbley [this message]
2018-08-10 3:17 ` Brad Bishop
2018-08-10 20:44 ` Dave Cobbley
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=fe79284e-e3d6-a71f-f055-6bcbe899fbd5@linux.intel.com \
--to=david.j.cobbley@linux.intel.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=prashanth.giri@dell.com \
--cc=sachit_bakshi@dell.com \
/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.