From: Bhupesh Sharma <bhupesh.sharma@nxp.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [RFC V2] EDK2 Platform Proposal
Date: Wed, 5 Oct 2016 06:11:26 +0000 [thread overview]
Message-ID: <AM4PR0401MB2289FD75D8BDD81CF1E517A588C40@AM4PR0401MB2289.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F56481B53B@ORSMSX113.amr.corp.intel.com>
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Kinney, Michael D
> Sent: Friday, September 23, 2016 2:25 AM
> Hello,
>
>
>
> Here is the V2 version of the proposal for the edk2-platforms repo.
>
>
>
> Changes from V1:
>
> ================
>
> * edk2-platform is not a fork of edk2.
>
> * edk2-platforms branches contain CPU, Chipset, SoC, and platform
> specific
>
> packages
>
> * edk2-plaforms/master contains all open platforms that are synced with
>
> edk2/master.
>
> * Each edk2-platforms branch may support many platforms (not just one)
>
> * Use PACKAGES_PATH to do builds using packages from multiple
> repositories
>
> * Update edk2-platforms branch naming to clearly identify platforms
> that
>
> are considered stable and platforms that are under active
> development.
>
> * edk2 developers may be required to verify platforms in edk2-platforms
>
> builds as part of test criteria. Especially platforms that are
> intended
>
> to be used with edk2/master in edk2-platforms/stable-* branches.
>
>
>
> =================
>
>
>
> Similar to edk2-staging, we also have a need to manage platforms
>
> that have been ported to edk2. Jordan has created a repository
>
> called edk2-platforms and has created a branch for the
>
> minnowboard-max that uses a validated release of the UDK 2015 for
>
> the dependent packages:
>
>
>
> https://github.com/tianocore/edk2-platforms
>
>
>
> https://github.com/tianocore/edk2-platforms/tree/minnowboard-max-
> udk2015
[Bhupesh] This link seems broken. I get a 404 error while trying to acess
this branch. Does it require some special privileges.
Regards,
Bhupesh
[snip..]
next prev parent reply other threads:[~2016-10-05 6:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 20:54 [RFC V2] EDK2 Platform Proposal Kinney, Michael D
2016-09-28 22:22 ` Leif Lindholm
2016-09-28 22:27 ` Andrew Fish
2016-09-29 22:21 ` Kinney, Michael D
2016-09-29 22:15 ` Kinney, Michael D
2016-10-14 7:14 ` Kinney, Michael D
2016-10-14 7:25 ` Kinney, Michael D
2016-10-14 12:59 ` Leif Lindholm
2016-10-14 15:48 ` Kinney, Michael D
2016-10-05 6:11 ` Bhupesh Sharma [this message]
2016-10-05 13:23 ` Richardson, Brian
2016-10-05 14:16 ` Sakar Arora
2016-10-10 19:22 ` Leif Lindholm
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=AM4PR0401MB2289FD75D8BDD81CF1E517A588C40@AM4PR0401MB2289.eurprd04.prod.outlook.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