From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Martin Wilck <mwilck@suse.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
Date: Mon, 9 Apr 2018 19:29:08 +0200 [thread overview]
Message-ID: <9ad33b55-17fc-9ed9-ca11-2be0e11a7b1f@gmail.com> (raw)
In-Reply-To: <1523289440.3525.27.camel@suse.com>
On 04/09/2018 05:57 PM, Martin Wilck wrote:
> There are >130 files in the multipath-tools source code which don't
> have a license header. So far my *assumption* was that these files were
> covered by COPYING, which used to be LGPLv2.0.
They are under their _original_ licence. Nothing was changed inside
the files.
> By changing COPYING to
> GPLv2.0, you effectively changed the license of all these files from
> LPGLv2.0 to GPLv2.0
There is no evidence of that in any place. All references to the COPYING file are
external files/code, with GPL licence.
$ git grep COPYING
libdmmp/docs/kernel-doc:## Please read the COPYING file for more information ##
libmultipath/alias.c: * See the file COPYING included with this distribution for more details.
libmultipath/file.c: * See the file COPYING included with this distribution for more details.
third-party/valgrind/drd.h: otherwise indicated. See the COPYING file in the source
third-party/valgrind/drd.h: COPYING file in the source distribution for details.
third-party/valgrind/valgrind.h: otherwise indicated. See the COPYING file in the source
third-party/valgrind/valgrind.h: COPYING file in the source distribution for details.
next prev parent reply other threads:[~2018-04-09 17:29 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 [this message]
2018-04-09 19:08 ` Martin Wilck
2018-04-09 20:38 ` Christophe Varoqui
2018-04-09 21:25 ` Martin Wilck
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=9ad33b55-17fc-9ed9-ca11-2be0e11a7b1f@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=mwilck@suse.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