From: Wei Liu <wei.liu2@citrix.com>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: xuquan8@huawei.com, wei.liu2@citrix.com,
ian.jackson@eu.citrix.com, samuel.thibault@ens-lyon.org,
xen-devel@lists.xenproject.org, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH 0/4] Clarify License information : m4, stubdom, tools/blktap2, xen/crypto
Date: Mon, 15 Aug 2016 13:11:01 +0100 [thread overview]
Message-ID: <20160815121101.GR20641@citrix.com> (raw)
In-Reply-To: <1471023156-2194-1-git-send-email-lars.kurth@citrix.com>
Cc Ian's correct email address
On Fri, Aug 12, 2016 at 06:32:32PM +0100, Lars Kurth wrote:
> This series contains some of the easier license clean-up cases, which can be fixed
> by adding COPYING files or README.source files. The series specially contains:
>
> xen/crypto and xen/include/crypto
> Added a README.source file
> Does not need a COPYING file: all files are imported
>
> m4
> Updated README.source to include ax_compare_version.m4
> Does not need a COPYING file: all files are GPLv2
> Exceptions are exclusively from imported files: GPLv2+
> and Laurikari (https://enterprise.dejacode.com/license_library/Demo/laurikari/)
>
> stubdom
> Added a COPYING file as a boilerplate to explain license oddities in this directory
> Added a vtpm/COPYING file which contains MIT licensed files only
> Added a vtpmmgr/README.source file which contains many BSD-3-Clause files only,
> that originally came from tools/vtpm_manager
>
> tools/blktap2
> Added a COPYING file
> There is some complexity here, but I believe it is not necessary to fix this at this
> stage, as for some time we were discussing to remove blktap2.
>
> --
> 2.5.4 (Apple Git-61)
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-08-15 12:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 17:32 [PATCH 0/4] Clarify License information : m4, stubdom, tools/blktap2, xen/crypto Lars Kurth
2016-08-12 17:32 ` [PATCH 1/4] Add information on sources for vmac.* and rijndael.* Lars Kurth
2016-08-12 17:32 ` [PATCH 2/4] Added source of ax_compare_version.m4 to import log Lars Kurth
2016-08-24 9:37 ` Wei Liu
2016-08-12 17:32 ` [PATCH 3/4] [STUBDOM] Added COPYING files and README.source files Lars Kurth
2016-08-24 10:10 ` Wei Liu
2016-08-24 10:31 ` Wei Liu
2016-08-24 12:43 ` Lars Kurth
2016-08-12 17:32 ` [PATCH 4/4] blktap2: Added COPYING file Lars Kurth
2016-08-24 9:38 ` Wei Liu
2016-08-15 12:11 ` Wei Liu [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-all 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=20160815121101.GR20641@citrix.com \
--to=wei.liu2@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.jackson@eu.citrix.com \
--cc=lars.kurth@citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xuquan8@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.