From: Martin Wilck <mwilck@suse.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 2/2] multipath-tools: add GPLv2 as COPYING
Date: Wed, 28 Mar 2018 00:04:52 +0200 [thread overview]
Message-ID: <1522188292.13140.54.camel@suse.com> (raw)
In-Reply-To: <20180327182819.20163-2-xose.vazquez@gmail.com>
On Tue, 2018-03-27 at 20:28 +0200, Xose Vazquez Perez wrote:
> Source directly from: https://www.gnu.org/licenses/old-licenses/gpl-2
> .0.txt
>
> 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>
Do you plan to add a README.COPYING or similar explaining which license
applies to what part of the code?
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-03-27 22:04 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 [this message]
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
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=1522188292.13140.54.camel@suse.com \
--to=mwilck@suse.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.