From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Varun Sethi <V.Sethi@nxp.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Peter W Newton <peter.newton@nxp.com>
Subject: Re: EDK II license query
Date: Fri, 14 Jul 2017 16:10:31 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5A7D5B94A@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <HE1PR04MB30025817B77AC2EB7972CFAEE8AD0@HE1PR04MB3002.eurprd04.prod.outlook.com>
Varun,
Right now, all the license files are one level down in each
Package in the edk2 repository.
I am actually preparing some patches to address this issue
since all of the packages have the same license. There are
a few files/directories that are covered by a different license
(e.g. MIT), but the license file for those is in the directory
with the content that covered by that other license.
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On
> Behalf Of Varun Sethi
> Sent: Friday, July 14, 2017 4:18 AM
> To: edk2-devel@lists.01.org
> Cc: Peter W Newton <peter.newton@nxp.com>
> Subject: [edk2] EDK II license query
>
> Hi,
> I don't see a top-level license in the EDKII repository. As per
> the following link EDKII uses BSD license.
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II
>
> Is there a specific reason for not having a top-level license in
> the EDK II repository?
>
> Regards
> Varun
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-07-14 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 11:17 EDK II license query Varun Sethi
2017-07-14 16:09 ` Marvin H?user
2017-07-14 16:10 ` Kinney, Michael D [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=E92EE9817A31E24EB0585FDF735412F5A7D5B94A@ORSMSX113.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