Managing openbmc with subtree

[Dave Cobbley]

On 08/09/2018 08:17 PM, Brad Bishop wrote:
>> On Aug 9, 2018, at 8:31 PM, Dave Cobbley <david.j.cobbley at linux.intel.com> wrote:
>>
>>>> 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?
> Yes, exactly.
>
>>> -Dave
Brad,
Can you make new github projects for the following? Just about 
everything else has a repo for subtrees.

meta-arm/
meta-x86/
meta-nuvoton/
meta-intel/
meta-mellanox/
meta-portwell/
meta-quanta/
meta-ibm/
meta-ingrasys/
meta-inventec/
meta-rackspace/

Subtress that already have a repo:
*poky/
*meta-openembedded/
*meta-security/
*meta-openpower/
*meta-phosphor/
*meta-aspeed/
*meta-raspberrypi/
*meta-qualcomm/ -- is this qualcomm-misc?

Should we need to rename qualcomm-mist to meta-qualcomm?

Additionally, looking at next steps for this:
- Modify the build script to run a full yocto build with each individual 
subtree review.
- Need to create a script which will merge code into the top level 
openbmc/openbmc
     Still trying to image what this script will look like, for example:
     $ git clone openbmc/openbmc
     $ git cherry-pick --strategy=subtree -Xsubtree=$SubtreePath $SubtreeSHA
     $ git push #does it need to push for review? I'm assuming at this 
point the build had already run on the subtree repo...
- How to handle existing reviews? Do we need a script to keep the 
subtrees up to date?

Are there any other steps I am missing?

Thanks,
-Dave