From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Daryl McDaniel (edk2-lists@mc2research.org)"
<edk2-lists@mc2research.org>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"Andrew Fish (afish@apple.com)" <afish@apple.com>,
"Laszlo Ersek <lersek@redhat.com> (lersek@redhat.com)"
<lersek@redhat.com>
Subject: Re: [edk2][edk2-libc/master V2]Request to add new edk2-libc repository
Date: Fri, 26 Apr 2019 02:49:02 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515CBCC083B7@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9C9E6F4@ORSMSX113.amr.corp.intel.com>
The 3 new commits look good.
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
> -----Original Message-----
> From: Kinney, Michael D
> Sent: Thursday, April 25, 2019 5:56 PM
> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: Carsey, Jaben <jaben.carsey@intel.com>; Daryl McDaniel (edk2-
> lists@mc2research.org) <edk2-lists@mc2research.org>;
> leif.lindholm@linaro.org; Andrew Fish (afish@apple.com)
> <afish@apple.com>; Laszlo Ersek <lersek@redhat.com>
> (lersek@redhat.com) <lersek@redhat.com>
> Subject: [edk2][edk2-libc/master V2]Request to add new edk2-libc repository
> Importance: High
>
> Hello,
>
> New in V2
> =========
> * Add details to Readme.md on how the history for these
> three packages was exported from the edk2 repository
> using git filter-branch.
> * Remove redundant content in edk2-libc Readme.md and
> Maintainters.txt and instead point to content in edk2
> repository.
> * Mark the sections of Maintainers.txt that need further
> discussion as TBD.
> * Update installation and build instructions in the
> Readme.txt files in AppPkg and StdLib.
> * Fix a warning in StdLib when building with VS2015.
> ========
>
> There were no objections to the following RFC to add a new edk2-libc
> repository.
>
> https://edk2.groups.io/g/devel/message/35211
>
> I have entered the following Feature Request Bugzilla
>
> https://bugzilla.tianocore.org/show_bug.cgi?id=1734
>
> I have posted a version of the edk2-libc repository for review at the following
> location. It includes all the history for the three packages from the edk2
> repository.
>
> https://github.com/mdkinney/edk2-libc/tree/master_V2
>
> Please review this branch. There are 3 additional commits:
>
> * Update the Readme.md and Maintainers.txt that scopes them
> to this new edk2-libc repository.
>
> https://github.com/mdkinney/edk2-
> libc/commit/62cfdf929f15edba7f7bcbbdb01e4dc50d2c81a7
>
> * Update Readme.txt in AppPkg and StdLib to describe how to
> install both the edk2-libc repository and the edk2
> repository and set PACKAGES_PATH to support builds.
>
> https://github.com/mdkinney/edk2-
> libc/commit/d004f93626b3bb962c24500db6ec7284db074c9a
>
> * Fix a minor issue that removes warnings when building
> edk2-libc packages with VS2015 toolchains.
>
> https://github.com/mdkinney/edk2-
> libc/commit/145d262e94182a6b4631e0b6df5bc5d67e209931
>
> Best regards,
>
> Mike
next prev parent reply other threads:[~2019-04-26 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 0:55 [edk2][edk2-libc/master V2]Request to add new edk2-libc repository Michael D Kinney
2019-04-26 2:49 ` Carsey, Jaben [this message]
2019-04-26 22:17 ` [edk2-devel] " Laszlo Ersek
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=CB6E33457884FA40993F35157061515CBCC083B7@FMSMSX103.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