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 v2 0/2] Clarify License information : stubdom, tools/blktap2
Date: Mon, 26 Sep 2016 14:30:00 +0100 [thread overview]
Message-ID: <20160926133000.GA16004@citrix.com> (raw)
In-Reply-To: <1474892194-7180-1-git-send-email-lars.kurth@citrix.com>
On Mon, Sep 26, 2016 at 01:16: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:
>
> 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.
>
I will commit this series on Friday if I hear no objection by then.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-26 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 12:16 [PATCH v2 0/2] Clarify License information : stubdom, tools/blktap2 Lars Kurth
2016-09-26 12:16 ` [PATCH v2 0/1] [STUBDOM] Added COPYING files and README.source files Lars Kurth
2016-09-26 12:34 ` Wei Liu
2016-09-26 12:16 ` [PATCH 2/2] blktap2: Added COPYING file Lars Kurth
2016-09-26 12:34 ` Wei Liu
2016-09-26 13:30 ` Wei Liu [this message]
2016-09-30 11:11 ` [PATCH v2 0/2] Clarify License information : stubdom, tools/blktap2 Wei Liu
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=20160926133000.GA16004@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.jackson@eu.citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).