From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>,
Martin Wilck <mwilck@suse.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 1/2] multipath-tools: move COPYING to COPYING.LESSER
Date: Tue, 10 Apr 2018 23:38:19 +0200 [thread overview]
Message-ID: <9c22169e-dfe5-e442-4612-74783e95e026@gmail.com> (raw)
In-Reply-To: <CABr-GneDAcFMVJKfrLJX6fBe5F-e-G_Sh_f1XvSwFH-0umM1Ew@mail.gmail.com>
On 04/09/2018 10:38 PM, Christophe Varoqui wrote:
> 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 ?
As Martin checked recently, there are four licences used in the code.
Put all of them in a LICENSES/ directory is clearer.
And do a link from LICENSES/LGPL-2.0 to COPYING, or LICENSE.default, ...
to indicate the default one.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2018-04-10 21:38 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
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 [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=9c22169e-dfe5-e442-4612-74783e95e026@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 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.