From: "Kubacki, Michael A" <michael.a.kubacki@intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-platforms] [RFC] Migrate devel-MinPlatform branch to master branch
Date: Wed, 24 Apr 2019 17:24:15 +0000 [thread overview]
Message-ID: <49AB4ACB9627B8468F29D589A27B7455888D2B03@ORSMSX122.amr.corp.intel.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E42FD4B@SHSMSX104.ccr.corp.intel.com>
BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1748
> -----Original Message-----
> From: Gao, Liming
> Sent: Wednesday, April 24, 2019 12:22 AM
> To: devel@edk2.groups.io; Kubacki, Michael A
> <michael.a.kubacki@intel.com>
> Subject: RE: [edk2-platforms] [RFC] Migrate devel-MinPlatform branch to
> master branch
>
> Michael:
> I think this change is good. Could you submit one BZ for it?
>
> Thanks
> Liming
> >-----Original Message-----
> >From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> >Kubacki, Michael A
> >Sent: Friday, April 19, 2019 5:12 AM
> >To: 'devel@edk2.groups.io' <devel@edk2.groups.io>
> >Subject: [edk2-devel] [edk2-platforms] [RFC] Migrate devel-MinPlatform
> >branch to master branch
> >
> >Hello,
> >
> >This RFC proposes moving the content on the devel-MinPlatform branch in
> >the edk2-platforms repository to the master branch in the
> >edk2-platforms repository.
> >
> >The devel-MinPlatform branch has been used for the initial development
> >of an EDK II based platform design referred to as "Minimum Platform".
> >This design is intended to provide a structured approach to introducing
> >Intel platform code into open source in a consistent manner.
> >
> >For more information about the EDK II Minimum Platform, please refer to
> >the Readme.md in devel-MinPlatform.
> >https://github.com/tianocore/edk2-platforms/blob/devel-
> >MinPlatform/ReadMe.md
> >
> >The following packages would be added in Platform/Intel:
> > * Generic packages:
> > * AdvancedFeaturePkg
> > * MinPlatformPkg
> > * Board-specific packages:
> > * ClevoOpenBoardPkg
> > * KabylakeOpenBoardPkg
> > * PurleyOpenBoardPkg
> >
> >The following packages would be added in Silicon/Intel:
> > * KabylakeSiliconPkg
> > * LewisburgPkg
> > * PurleyRcPkg
> > * PurleySktPkg
> >
> >The following growth is expected over time:
> > * Platform/Intel - Additional board packages for Intel reference boards
> > including support for some pre-existing product releases
> > * AdvancedFeaturePkg - Additional modular features capable of being used
> > in board packages
> > * Silicon/Intel - Additional silicon packages roughly keeping 1:1 parity
> > with board packages
> >
> >We hope the content will enable others to add new board packages and
> >advanced features over time.
> >
> >The result of the change is available here for reference:
> >https://github.com/lgao4/edk2-platforms
> >
> >Regards,
> >Michael
> >
> >
next prev parent reply other threads:[~2019-04-24 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 21:11 [edk2-platforms] [RFC] Migrate devel-MinPlatform branch to master branch Kubacki, Michael A
2019-04-24 7:22 ` Liming Gao
2019-04-24 17:24 ` Kubacki, Michael A [this message]
2019-05-02 15:04 ` [edk2-devel] " Leif Lindholm
2019-05-02 21:15 ` Kubacki, Michael A
2019-05-04 0:32 ` Kubacki, Michael A
2019-05-06 8:22 ` Liming Gao
2019-05-07 2:19 ` Kubacki, Michael A
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-list 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=49AB4ACB9627B8468F29D589A27B7455888D2B03@ORSMSX122.amr.corp.intel.com \
--to=devel@edk2.groups.io \
/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