linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: linux-spdx@vger.kernel.org
Subject: [ASIS-5 patch 0/2] Deep review of 'AS IS' disclaimers - part 5
Date: Wed, 05 Jun 2019 16:10:31 +0200	[thread overview]
Message-ID: <20190605141031.265039392@linutronix.de> (raw)

This is the fifth variant of disclaimer modifications.

Standard disclaimer:

    this program is distributed in the hope that it will be useful
    but without any warranty without even the implied warranty of
    merchantability or fitness for a particular purpose

Modified disclaimer:

    this software is provided as is and without any express or implied
    warranties including without limitation the implied warranties of
    merchantability and fitness for a particular purpose

So as with the previous 4, I don't see anything contradicting or
substantially different.

In case we agree on that, I would amend the changelogs of the individual
patches with a paragraph explaining our conclusion. Something along the
lines:

    The pattern deviates from the standard GPLv2 disclaimer, but the
    modifications do not expand beyond the standard disclaimer and the NO
    WARRANTY section of the GPLv2. So replacing the license notice
    including the modified disclaimer with the SPDX license identifier
    results in the same protections and conditions.

Feel free to suggest better wording or deeper explanation.

Thanks,

        tglx


             reply	other threads:[~2019-06-05 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 14:10 Thomas Gleixner [this message]
2019-06-05 14:10 ` [ASIS-5 patch 1/2] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 298 Thomas Gleixner
2019-06-05 17:05   ` Enrico Weigelt, metux IT consult
2019-06-08 19:44   ` Allison Randal
2019-06-05 14:10 ` [ASIS-5 patch 2/2] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 302 Thomas Gleixner
2019-06-05 17:06   ` Enrico Weigelt, metux IT consult
2019-06-08 19:44   ` Allison Randal
2019-06-08 19:42 ` [ASIS-5 patch 0/2] Deep review of 'AS IS' disclaimers - part 5 Allison Randal
2019-06-12  4:58   ` Richard Fontana

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=20190605141031.265039392@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-spdx@vger.kernel.org \
    /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).