From: "Jayaprakash, N" <n.jayaprakash@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Jayaprakash, N" <n.jayaprakash@intel.com>
Cc: Rebecca Cran <rebecca@nuviainc.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2-libc Patch 1/1] edk2-libc/Readme.md: Updated Readme.md with Python 3.6.8 License details
Date: Thu, 9 Sep 2021 06:12:04 +0000 [thread overview]
Message-ID: <DM6PR11MB3337FCE3D44BB2DEFEB6B1B3EED59@DM6PR11MB3337.namprd11.prod.outlook.com> (raw)
In-Reply-To: <16A2E7244BB60FEC.20213@groups.io>
Hello Rebecca,
Would you be able to review and merge this change?
Regards,
JP
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Jayaprakash, N
Sent: 08 September 2021 22:24
To: devel@edk2.groups.io
Cc: Rebecca Cran <rebecca@nuviainc.com>; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: [edk2-devel] [edk2-libc Patch 1/1] edk2-libc/Readme.md: Updated Readme.md with Python 3.6.8 License details
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3611
This commit contains updates made to the Readme.md file of edk2-libc repo to add the Python 3.6.8 license at appropriate section in the file
Cc: Rebecca Cran <rebecca@nuviainc.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
---
Readme.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/Readme.md b/Readme.md
index 341be14..0012cd5 100644
--- a/Readme.md
+++ b/Readme.md
@@ -24,6 +24,7 @@ contains the following components that are covered by additional licenses:
* [AppPkg/Applications/Python/Python-2.7.2/Tools/pybench](AppPkg/Applications/Python/Python-2.7.2/Tools/pybench/LICENSE)
* [AppPkg/Applications/Python/Python-2.7.2](AppPkg/Applications/Python/Python-2.7.2/LICENSE)
* [AppPkg/Applications/Python/Python-2.7.10](AppPkg/Applications/Python/Python-2.7.10/LICENSE)
+*
+[AppPkg/Applications/Python/Python-3.6.8](AppPkg/Applications/Python/Py
+thon-3.6.8/LICENSE)
The EDK II LIBC Project is composed of packages. The maintainers for each package are listed in [Maintainers.txt](Maintainers.txt).
--
2.32.0.windows.2
next prev parent reply other threads:[~2021-09-09 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 16:54 [edk2-libc Patch 0/1] updated to Readme.md of edk2-libc with py 3.6.8 License file details Jayaprakash, N
2021-09-08 16:54 ` [edk2-libc Patch 1/1] edk2-libc/Readme.md: Updated Readme.md with Python 3.6.8 License details Jayaprakash, N
2021-09-10 17:31 ` Rebecca Cran
[not found] ` <16A2E7244BB60FEC.20213@groups.io>
2021-09-09 6:12 ` Jayaprakash, N [this message]
2021-09-10 17:30 ` [edk2-devel] " Rebecca Cran
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=DM6PR11MB3337FCE3D44BB2DEFEB6B1B3EED59@DM6PR11MB3337.namprd11.prod.outlook.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