From: "Rebecca Cran" <rebecca@nuviainc.com>
To: devel@edk2.groups.io, maciej.rabeda@linux.intel.com
Subject: Re: [edk2-devel] "StdLibPkg" branch on edk2-staging
Date: Wed, 28 Jul 2021 09:59:14 -0600 [thread overview]
Message-ID: <7be48f7f-9c84-e602-1792-63b7da42307b@nuviainc.com> (raw)
In-Reply-To: <5f539192-4c86-0d1e-ddaf-63c3b3dd58aa@linux.intel.com>
I think it's mostly been abandoned, and people are expected to use
native UEFI functions instead. Personally I'd like to see it continue to
be maintained.
--
Rebecca Cran
On 7/28/21 9:45 AM, Maciej Rabeda wrote:
> Naturally. Since it is there, why is it not used for brotli, openssl
> in CryptoPkg or jansson in RedfishPkg?
>
> On 28-Jul-21 17:34, Rebecca Cran wrote:
>> Are you aware of the edk2-libc project at
>> https://github.com/tianocore/edk2-libc ?
>>
>>
>
>
>
>
>
>
next prev parent reply other threads:[~2021-07-28 15:59 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 [this message]
2021-07-28 22:25 ` Tim Lewis
2021-07-28 22:44 ` Rebecca Cran
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=7be48f7f-9c84-e602-1792-63b7da42307b@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