From: Martin Wilck <mwilck@suse.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH RFC] multipath-tools: create LICENSES dir with the text of all used licences
Date: Tue, 10 Apr 2018 09:25:16 +0200 [thread overview]
Message-ID: <1523345116.3525.70.camel@suse.com> (raw)
In-Reply-To: <20180409165104.6936-1-xose.vazquez@gmail.com>
On Mon, 2018-04-09 at 18:51 +0200, Xose Vazquez Perez wrote:
> Move COPYING -> LICENSES/GPL-2.0
> Move COPYING.LESSER -> LICENSES/LGPL-2.0
>
> Add GPL-3.0 and LGPL-2.1 to the LICENSES dir.
> Source directly from:
> https://www.gnu.org/licenses/gpl-3.0.txt
> https://www.gnu.org/licenses/old-licenses/lgpl-2.1.txt
>
> Cc: Martin Wilck <mwilck@suse.com>
> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
> Cc: device-mapper development <dm-devel@redhat.com>
> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
> ---
I like this.
Acked-by: Martin Wilck <mwilck@suse.com>
I suggest to add my posting from yesterday ("multipath-tools 0.7.6
fossology license assessment") as "README.licenses".
With these changes, we'd be in a fine state for the time being.
Actual license changes can be considered for the long term, but don't
need to be - the current situation is complex but not actually
problematic. SPDX tags can be added to source files by and by, as we
see fit.
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2018-04-10 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 16:51 [PATCH RFC] multipath-tools: create LICENSES dir with the text of all used licences Xose Vazquez Perez
2018-04-10 7:25 ` Martin Wilck [this message]
2018-04-10 15:42 ` Xose Vazquez Perez
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=1523345116.3525.70.camel@suse.com \
--to=mwilck@suse.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=xose.vazquez@gmail.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.