From: "You, Benjamin" <benjamin.you@intel.com>
To: "You, Benjamin" <benjamin.you@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [staging/UEFIPayload]: Creating a new feature branch UEFIPayload in edk2-staging
Date: Sat, 15 Sep 2018 15:17:27 +0000 [thread overview]
Message-ID: <E748835C6D8DB54B8E8AF33091ECC57C6225D14C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <E748835C6D8DB54B8E8AF33091ECC57C6225CFB8@SHSMSX103.ccr.corp.intel.com>
Hi,
The UEFIPayload feature branch has been created at:
https://github.com/tianocore/edk2-staging/tree/UEFIPayload
Thanks,
- ben
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of You,
> Benjamin
> Sent: Friday, September 14, 2018 9:47 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [staging/UEFIPayload]: Creating a new feature branch
> UEFIPayload in edk2-staging
>
> Hi,
>
> A new feature branch "UEFIPayload" is being created in edk2-staging.
>
> UEFI Payload (UefiPayloadPkg) aims to be an upgrade to CorebootModulePkg
> and CorebootPayloadPkg
>
> UEFI Payload has some new features:
> * Supporting Slim Bootloader in addition to Coreboot
> * Source level configuration using .ini format
> * User Extension using simple "C" codes
> * Platform support library for adding platform specific codes
>
> A draft version can be found at https://github.com/BenjaminYou/UEFIPayload
>
> Thanks,
>
> - ben
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2018-09-15 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 13:47 [staging/UEFIPayload]: Creating a new feature branch UEFIPayload in edk2-staging You, Benjamin
2018-09-14 17:37 ` Kinney, Michael D
2018-09-15 15:26 ` You, Benjamin
2018-09-15 15:17 ` You, Benjamin [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=E748835C6D8DB54B8E8AF33091ECC57C6225D14C@SHSMSX103.ccr.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