public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Guo, Mang" <mang.guo@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Lu, ShifeiX A" <shifeix.a.lu@intel.com>,
	"Wei, David" <david.wei@intel.com>
Subject: Re: [Patch][edk2-platforms/minnowboard-max-udk2017] Add new platform branch minnowboard-max-udk2017
Date: Mon, 31 Jul 2017 15:49:03 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5A7D60937@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <22D2C85ED001C54AA20BFE3B0E4751D15252311B@SHSMSX103.ccr.corp.intel.com>

Guo Mang,

A platform in the edk2-platforms repository should not contain
the packages from the edk2 repository.

Instead, the instructions for the platform should require both
the edk2 repo and the edk2-platform repo to be cloned with the
correct branches checked out and PACKAGES_PATH set so the build 
tools can use packages from both branches.

This maximizes the reuse of the code from the edk2 repo and 
minimizes the amount of code in a platform branch in edk2-platforms.

Also, the branch name does not follow the naming convention.  Please
see: https://github.com/tianocore/edk2-platforms/blob/about/Readme.md

Thanks,

Mike

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On
> Behalf Of Guo, Mang
> Sent: Monday, July 31, 2017 2:26 AM
> To: edk2-devel@lists.01.org
> Cc: Lu, ShifeiX A <shifeix.a.lu@intel.com>; Wei, David
> <david.wei@intel.com>
> Subject: [edk2] [Patch][edk2-platforms/minnowboard-max-udk2017]
> Add new platform branch minnowboard-max-udk2017
> 
> Create a new branch (minnowboard-max-udk2017) on edk2-platforms
> for MinnowBoard Max. This code base is based on UDK2017 core
> packages.
> Code is ready in https://github.com/mangguo321/edk2-
> platforms/tree/minnowboard-max-udk2017
> 
> Contributed-under: TianoCore Contribution Agreement 1.0
> 
> Signed-off-by: Guo Mang <mang.guo@intel.com>
> ---
>  ReadMe.MD | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>  create mode 100644 ReadMe.MD
> 
> diff --git a/ReadMe.MD b/ReadMe.MD
> new file mode 100644
> index 0000000..8dcca92
> --- /dev/null
> +++ b/ReadMe.MD
> @@ -0,0 +1,10 @@
> +# MINNOWBOARD MAX/TURBOT PLATFORM FIRMWARE
> +
> +This UEFI firmware is designed for the open hardware
> MinnowBoard Max/Turbot platforms using
> +the Intel(R) Atom(tm) Processor E3800 Series, based on UDK2017
> core packages.
> +
> +http://minnowboard.org/ -- Platform Information, including
> schematics and information on where to purchase boards.
> +
> +https://firmware.intel.com/projects/minnowboard-max -- Release
> notes, pre-built release/debug binaries, build instructions, and
> binary objects required to compile firmware.
> +
> +
> --
> 2.10.1.windows.1
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2017-07-31 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31  9:25 [Patch][edk2-platforms/minnowboard-max-udk2017] Add new platform branch minnowboard-max-udk2017 Guo, Mang
2017-07-31 15:49 ` Kinney, Michael D [this message]

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=E92EE9817A31E24EB0585FDF735412F5A7D60937@ORSMSX113.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