From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Benjamin Marzinski <bmarzins@redhat.com>, Martin Wilck <mwilck@suse.com>
Cc: device-mapper development <dm-devel@redhat.com>, fge@redhat.com
Subject: Re: multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer)
Date: Wed, 28 Mar 2018 00:24:53 +0200 [thread overview]
Message-ID: <904fd737-b8ff-016f-e33a-5d833ef33c3a@gmail.com> (raw)
In-Reply-To: <20180326160705.GM3103@octiron.msp.redhat.com>
On 03/26/2018 06:07 PM, Benjamin Marzinski wrote:
> If we can limit the project to two (or if necessary 3) licenses, we can
> just include all the license files, and explain what applies to what
> in the README. I haven't really looked at how other projects that have
> multiple licenses for parts of their code do things, so perhaps there is
> a more standard way.
Multiple licences, for modules, are accepted in the Linux kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/module.h#n171
And the SPDX License Identifier is being used:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/license-rules.rst
next prev parent reply other threads:[~2018-03-27 22:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 20:50 [PATCH] multipath-tools: replace FSF address with a www pointer Xose Vazquez Perez
2018-03-19 21:37 ` Martin Wilck
2018-03-23 18:28 ` Xose Vazquez Perez
2018-03-23 20:30 ` multipath-tools licenses (was Re: [PATCH] multipath-tools: replace FSF address with a www pointer) Martin Wilck
2018-03-26 11:04 ` Hannes Reinecke
2018-03-26 12:36 ` Martin Wilck
2018-03-26 14:02 ` Martin Wilck
2018-03-26 14:15 ` Martin Wilck
2018-03-26 16:07 ` Benjamin Marzinski
2018-03-26 16:16 ` Martin Wilck
2018-03-27 22:24 ` Xose Vazquez Perez [this message]
2018-03-28 15:14 ` Martin Wilck
2018-04-06 16:10 ` Xose Vazquez Perez
2018-04-06 16:25 ` Greg KH
2018-04-09 9:01 ` Martin Wilck
2018-04-10 13:56 ` Xose Vazquez Perez
2018-03-27 21:42 ` Xose Vazquez Perez
2018-03-27 21:53 ` Martin Wilck
2018-03-26 13:02 ` 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=904fd737-b8ff-016f-e33a-5d833ef33c3a@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=fge@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