From: Martin Wilck <mwilck@suse.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
Hannes
Subject: Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
Date: Mon, 09 Apr 2018 23:25:37 +0200 [thread overview]
Message-ID: <1523309137.3525.57.camel@suse.com> (raw)
In-Reply-To: <CABr-GneDAcFMVJKfrLJX6fBe5F-e-G_Sh_f1XvSwFH-0umM1Ew@mail.gmail.com>
On Mon, 2018-04-09 at 22:38 +0200, Christophe Varoqui wrote:
> Martin is right, the LGPL COPYING was added Sun May 1 15:05:22 2005.
> Every file added to the tree since then and up to Xose patch
> switching COPYING to GPL, and not explicitely licensed otherwise can
> be assumed to be covered by the LGPL.
> It was not intended to relicense any files, nor switch to GPL as the
> default license for new files without explicit licensing.
>
> Hope it clears the history part of the mess, and helps identify a
> solution.
>
> I see FSF recommends the COPYING+COPYING.LESSER file names, as Xose
> implemented. What if we just add a LICENSE file stating that files
> with no explicit copying* reference fall under the COPYING.LESSER ?
That'd be a good start. I'll shortly submit a license README file that
summarizes my research into the current situation. You can then decide
if you want to add it to the tree, or what else to do with it.
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-09 21:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 18:28 [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER Xose Vazquez Perez
2018-03-27 18:28 ` [PATCH 2/2] multipath-tools: add GPLv2 as COPYING Xose Vazquez Perez
2018-03-27 22:04 ` Martin Wilck
2018-03-28 19:31 ` Xose Vazquez Perez
2018-03-27 22:03 ` [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER Martin Wilck
2018-03-28 19:40 ` Xose Vazquez Perez
2018-03-28 19:54 ` Martin Wilck
2018-03-28 20:05 ` Xose Vazquez Perez
2018-03-28 20:14 ` Martin Wilck
2018-04-09 15:57 ` Martin Wilck
2018-04-09 17:29 ` Xose Vazquez Perez
2018-04-09 19:08 ` Martin Wilck
2018-04-09 20:38 ` Christophe Varoqui
2018-04-09 21:25 ` Martin Wilck [this message]
2018-04-09 22:37 ` multipath-tools 0.7.6 fossology license assessment Martin Wilck
2018-04-10 14:54 ` [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER Xose Vazquez Perez
2018-04-10 15:45 ` Christophe Varoqui
2018-04-10 21:38 ` 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=1523309137.3525.57.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.