From: Thomas Gleixner <tglx@linutronix.de>
To: Richard Fontana <rfontana@redhat.com>
Cc: linux-spdx@vger.kernel.org
Subject: Re: [patch 25/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 100
Date: Wed, 22 May 2019 15:42:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1905221539040.1637@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAC1cPGya89Pd2sS5xV_g6BAJycOzbXiEmKwP7AKbaYBEtywatg@mail.gmail.com>
On Wed, 22 May 2019, Richard Fontana wrote:
> On Wed, May 22, 2019 at 8:05 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> > neither [alan] [cox] [nor] [cymrunet]
> > [ltd] admit liability nor provide warranty for any of this software
> > this material is provided as is and at no charge
>
> Since some of these disclaimer statements are getting scrutinized,
> this one is also notable though it is more general than the other ones
> that have been called out. I think we should decide what to do about
> variously-worded warranty/liability disclaimer statements in general
> and consider this variety along with others. I assume SPDX previously
> never considered the problem of how to deal with license notices with
> various nonstandard disclaimer statements other than implicitly
> treating the ones in the GNU notice as conveying nothing more than
> what's already in the GPL/LGPL license texts.
>
> For the time being I am trying to call attention to anything that
> seems even slightly interestingly different from what's in the GNU
> notice ("WITHOUT ANY WARRANTY; without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE").
Right. The patcher keeps them around:
- * This program is free software; you can redistribute it and/or
- * modify it under the terms of the GNU General Public License
- * as published by the Free Software Foundation; either version
- * 2 of the License, or (at your option) any later version.
- *
* Neither Alan Cox nor CymruNet Ltd. admit liability nor provide
* warranty for any of this software. This material is provided
* "AS-IS" and at no charge.
But yes, the question is whether this is yet another license
variant^Wabomination.
Assumed that combining these magic disclaimers with the GPL text forms a
unique license then we probably (did not validate) double the number of
licenses in the kernel. We already have 80+ without those.
Thanks,
tglx
next prev parent reply other threads:[~2019-05-22 13:42 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 7:51 [patch 00/25] SPDX cleanup: batch 4 Thomas Gleixner
2019-05-22 7:51 ` [patch 01/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 76 Thomas Gleixner
2019-05-22 12:10 ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-05-22 12:47 ` Richard Fontana
2019-05-22 12:48 ` Kate Stewart
2019-05-23 21:04 ` Allison Randal
2019-05-22 7:51 ` [patch 02/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 77 Thomas Gleixner
2019-05-22 13:14 ` Richard Fontana
2019-05-22 14:35 ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-05-23 21:04 ` Allison Randal
2019-05-22 7:51 ` [patch 03/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 78 Thomas Gleixner
2019-05-22 13:15 ` Richard Fontana
2019-05-22 15:22 ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-05-23 21:06 ` Allison Randal
2019-05-22 7:51 ` [patch 04/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 79 Thomas Gleixner
2019-05-22 13:08 ` Richard Fontana
2019-05-22 15:36 ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-05-23 21:06 ` Allison Randal
2019-05-22 7:51 ` [patch 05/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 80 Thomas Gleixner
2019-05-22 13:07 ` Richard Fontana
2019-05-22 13:18 ` Greg KH
2019-05-23 21:20 ` Allison Randal
2019-05-24 2:40 ` Richard Fontana
2019-05-24 2:21 ` Richard Fontana
2019-05-24 5:54 ` Thomas Gleixner
2019-05-24 5:55 ` Greg KH
2019-05-24 16:29 ` Allison Randal
2019-05-22 7:51 ` [patch 06/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 81 Thomas Gleixner
2019-05-22 13:13 ` Richard Fontana
2019-05-22 16:42 ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-05-23 0:43 ` Kate Stewart
2019-05-23 21:10 ` Allison Randal
2019-05-22 7:51 ` [patch 07/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 82 Thomas Gleixner
2019-05-22 13:15 ` Richard Fontana
2019-05-22 16:43 ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-05-23 0:43 ` Kate Stewart
2019-05-23 21:11 ` Allison Randal
2019-05-22 7:51 ` [patch 08/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 83 Thomas Gleixner
2019-05-22 13:13 ` Richard Fontana
2019-05-22 21:58 ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-05-23 0:43 ` Kate Stewart
2019-05-23 21:12 ` Allison Randal
2019-05-22 7:51 ` [patch 09/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 84 Thomas Gleixner
2019-05-22 13:12 ` Richard Fontana
2019-05-22 21:58 ` Armijn Hemel - Tjaldur Software Governance Solutions
2019-05-23 21:22 ` Allison Randal
2019-05-22 7:51 ` [patch 10/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 85 Thomas Gleixner
2019-05-22 13:03 ` Richard Fontana
2019-05-22 7:51 ` [patch 11/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 86 Thomas Gleixner
2019-05-22 13:14 ` Richard Fontana
2019-05-23 21:41 ` Allison Randal
2019-05-22 7:51 ` [patch 12/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 87 Thomas Gleixner
2019-05-22 13:11 ` Richard Fontana
2019-05-22 13:46 ` Thomas Gleixner
2019-05-22 7:51 ` [patch 13/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 88 Thomas Gleixner
2019-05-22 13:11 ` Richard Fontana
2019-05-23 21:43 ` Allison Randal
2019-05-22 7:51 ` [patch 14/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 89 Thomas Gleixner
2019-05-22 13:12 ` Richard Fontana
2019-05-23 21:44 ` Allison Randal
2019-05-22 7:51 ` [patch 15/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 90 Thomas Gleixner
2019-05-22 13:06 ` Richard Fontana
2019-05-23 21:45 ` Allison Randal
2019-05-22 7:51 ` [patch 16/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 91 Thomas Gleixner
2019-05-22 12:48 ` Richard Fontana
2019-05-23 21:45 ` Allison Randal
2019-05-22 7:51 ` [patch 17/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 92 Thomas Gleixner
2019-05-22 13:02 ` Richard Fontana
2019-05-22 18:07 ` Thomas Gleixner
2019-05-22 7:51 ` [patch 18/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 93 Thomas Gleixner
2019-05-22 12:48 ` Richard Fontana
2019-05-23 21:48 ` Allison Randal
2019-05-22 7:51 ` [patch 19/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 94 Thomas Gleixner
2019-05-22 13:06 ` Richard Fontana
2019-05-23 21:48 ` Allison Randal
2019-05-22 7:51 ` [patch 20/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 95 Thomas Gleixner
2019-05-22 13:00 ` Richard Fontana
2019-05-23 21:49 ` Allison Randal
2019-05-22 7:51 ` [patch 21/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 96 Thomas Gleixner
2019-05-22 12:59 ` Richard Fontana
2019-05-23 21:50 ` Allison Randal
2019-05-22 7:51 ` [patch 22/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 97 Thomas Gleixner
2019-05-22 13:05 ` Richard Fontana
2019-05-23 21:50 ` Allison Randal
2019-05-22 7:51 ` [patch 23/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 98 Thomas Gleixner
2019-05-22 13:06 ` Richard Fontana
2019-05-23 21:51 ` Allison Randal
2019-05-22 7:51 ` [patch 24/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 99 Thomas Gleixner
2019-05-22 13:04 ` Richard Fontana
2019-05-22 7:51 ` [patch 25/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 100 Thomas Gleixner
2019-05-22 12:59 ` Richard Fontana
2019-05-22 13:42 ` Thomas Gleixner [this message]
2019-05-22 15:30 ` J Lovejoy
2019-05-23 22:05 ` Allison Randal
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=alpine.DEB.2.21.1905221539040.1637@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-spdx@vger.kernel.org \
--cc=rfontana@redhat.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;
as well as URLs for NNTP newsgroup(s).