Linux Device Mapper development
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: development <dm-devel@redhat.com>, device-mapper
Subject: Re: [PATCH] multipath-tools: replace FSF address with a www pointer
Date: Mon, 19 Mar 2018 22:37:38 +0100	[thread overview]
Message-ID: <1521495458.3798.138.camel@suse.com> (raw)
In-Reply-To: <20180310205002.3318-1-xose.vazquez@gmail.com>

On Sat, 2018-03-10 at 21:50 +0100, Xose Vazquez Perez wrote:
> Less prone to future modifications, and new FSF licences
> point exactly to this url: <http://www.gnu.org/licenses/>.
> 
> First clean up was done in 5619a39c433ac3d10a88079593cec1aa6472cbeb
> 
> Cc: Martin Wilck <mwilck@suse.com>
> 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>

IANAL, but AFAICS multipath-tools comes under GPLv2, and the GPLv2
still contains the original paragraph with the address. 

https://www.gnu.org/licenses/old-licenses/gpl-2.0.html#howto

Replacing this by the text from GPLv3, and using the "/licenses/" link,
which points to a page mostly devoted to GPLv3, might cause people to
think we're using GPLv3. I'm in favor of keeping the GPLv2 wording.

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

  reply	other threads:[~2018-03-19 21:37 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 [this message]
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
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=1521495458.3798.138.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox