From: "Rebecca Cran" <rebecca@nuviainc.com>
To: tim.lewis@insyde.com, devel@edk2.groups.io,
maciej.rabeda@linux.intel.com
Cc: Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] "StdLibPkg" branch on edk2-staging
Date: Wed, 28 Jul 2021 16:44:02 -0600 [thread overview]
Message-ID: <ee1c6fd7-72e1-2a42-19e1-fd92692975db@nuviainc.com> (raw)
In-Reply-To: <0fb201d783ff$75096c90$5f1c45b0$@insyde.com>
CC'ing the Tianocore stewards.
I've had problems getting a recent patch committed just to make
edk2-libc work against current edk2 master.
Tianocore stewards: do we need new or additional maintainers for
edk2-libc, or is there a plan to deprecate it?
The current maintainers are listed as:
StdLib, StdLibPrivateInternalFiles
W: https://github.com/tianocore/tianocore.github.io/wiki/StdLib
M: Daryl McDaniel <edk2-lists@mc2research.org>
M: Jaben Carsey <jaben.carsey@intel.com>
--
Rebecca Cran
On 7/28/21 4:25 PM, tim.lewis@insyde.com wrote:
> I would point out that there was significant work on libc in the past (see https://github.com/andreiw/UefiToolsPkg) but never any help to upstream these fixes, including making sure that many Linux tools can easily be ported. I myself have used it to port several BSD utilities over, but each time there will little nits with the existing port and even small patches were returned with "no current maintainer"
>
> In terms of making other projects use libc, I think the other objection was that it was never optimized for non-shell usage. Other projects (lie https://github.com/tianocore/edk2-staging/tree/CdePkg ) have tried to remedy this, but never with source checked in. But it allows support under PEI, DXE, etc.
>
> Tim
>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
> Sent: Wednesday, July 28, 2021 8:34 AM
> To: devel@edk2.groups.io; maciej.rabeda@linux.intel.com
> Subject: Re: [edk2-devel] "StdLibPkg" branch on edk2-staging
>
> Are you aware of the edk2-libc project at https://github.com/tianocore/edk2-libc ?
>
>
next prev parent reply other threads:[~2021-07-28 22:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 15:48 "StdLibPkg" branch on edk2-staging Maciej Rabeda
2021-07-28 15:34 ` [edk2-devel] " Rebecca Cran
2021-07-28 15:45 ` Maciej Rabeda
2021-07-28 15:59 ` Rebecca Cran
2021-07-28 22:25 ` Tim Lewis
2021-07-28 22:44 ` Rebecca Cran [this message]
2021-08-04 11:03 ` Leif Lindholm
2021-08-05 3:35 ` Andrew Fish
2021-08-05 4:14 ` Kilian Kegel
[not found] ` <16984DDFBF70DC40.16396@groups.io>
2021-08-11 13:19 ` Kilian Kegel
2021-11-14 19:51 ` CdePkgBlog 2021-11-14 Kilian Kegel
2021-11-22 16:31 ` [edk2-devel] " Maciej Rabeda
2021-11-24 20:21 ` Kilian Kegel
2021-11-24 22:50 ` Pedro Falcato
2021-11-28 20:35 ` CdePkgBlog 2021-11-18 Kilian Kegel
[not found] ` <16BBD01DEB5EF921.4083@groups.io>
2021-12-12 20:02 ` CdePkgBlog 2021-12-12 Kilian Kegel
2021-12-19 20:51 ` CdePkgBlog 2021-12-19 Kilian Kegel
2022-01-16 20:01 ` CdePkgBlog 2022-01-16 -- Introduction of the ACPICA port to UEFI Kilian Kegel
2021-11-30 10:09 ` [edk2-devel] CdePkgBlog 2021-11-14 Maciej Rabeda
[not found] ` <16BC4B25BB307B73.14741@groups.io>
2021-11-30 20:15 ` Maciej Rabeda
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=ee1c6fd7-72e1-2a42-19e1-fd92692975db@nuviainc.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