From: Allison Randal <allison@lohutok.net>
To: linux-spdx@vger.kernel.org
Subject: Re: [ASIS-5 patch 0/2] Deep review of 'AS IS' disclaimers - part 5
Date: Sat, 8 Jun 2019 15:42:45 -0400 [thread overview]
Message-ID: <7b8044bb-8df7-963a-95ce-38e15d97e691@lohutok.net> (raw)
In-Reply-To: <20190605141031.265039392@linutronix.de>
On 6/5/19 10:10 AM, Thomas Gleixner wrote:
> 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.
The added wording "as is" and "express or implied" was copied from
GPLv2, and so doesn't add any additional disclaimers.
Allison
next prev parent reply other threads:[~2019-06-08 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 14:10 [ASIS-5 patch 0/2] Deep review of 'AS IS' disclaimers - part 5 Thomas Gleixner
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 ` Allison Randal [this message]
2019-06-12 4:58 ` [ASIS-5 patch 0/2] Deep review of 'AS IS' disclaimers - part 5 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=7b8044bb-8df7-963a-95ce-38e15d97e691@lohutok.net \
--to=allison@lohutok.net \
--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).