From: Richard Fontana <rfontana@redhat.com>
To: Allison Randal <allison@lohutok.net>
Cc: linux-spdx@vger.kernel.org
Subject: Re: [GOODTITLE patch 0/8] Deep review of the 'good title' disclaimer variant
Date: Sun, 9 Jun 2019 23:28:22 -0400 [thread overview]
Message-ID: <CAC1cPGzpco=JYfZSE0BrEOdk1EGMpa0DOpBypZYw+aSxj0FtxA@mail.gmail.com> (raw)
In-Reply-To: <473c72f1-3be5-7af5-fcf0-027187b31100@lohutok.net>
On Sat, Jun 8, 2019 at 4:38 PM Allison Randal <allison@lohutok.net> wrote:
>
> On 6/5/19 11:00 AM, Thomas Gleixner wrote:
> > The following modified disclaimer is beyond my competence so I refrain from
> > commenting on it and leave it to our lawyer friends to make sense of it.
> >
> > 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 see the gnu general
> > public license for more details
> >
> > Modified 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 good title or non
> > infringement see the gnu general public license for more details
> >
> > The extra bit is: "good title or non infringement"
>
> My understanding is that the warranties of title and noninfringement are
> standard implied warranties, so GPLv2 already disclaims them by
> disclaiming any implied warranties. But, this seems more legally
> nuanced, so I'll wait to review until some of the lawyers comment.
Unfortunately it is not clear. Though this is not my view, one could
argue that the warranty disclaimer provision in GPLv2 itself is
inadequate to disclaim implied warranties that are not specifically
mentioned, based on commercial law in the US, or at least,
specifically, the implied warranties of title and noninfringement.
I would have to assume that anyone who bothered to add disclaimers of
the implied warranties of title and noninfringement into the standard
GNU GPL license notice (which does not mention them) did so because
they believed the standard language in the notice and the license
itself was -- or might be -- deficient.
I think therefore that either these disclaimer notices should be kept,
unless the original copyright holder associated with the notice agrees
otherwise.
Richard
prev parent reply other threads:[~2019-06-10 3:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 15:00 [GOODTITLE patch 0/8] Deep review of the 'good title' disclaimer variant Thomas Gleixner
2019-06-05 15:00 ` [GOODTITLE patch 1/8] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 66 Thomas Gleixner
2019-06-05 15:00 ` [GOODTITLE patch 2/8] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 107 Thomas Gleixner
2019-06-05 15:00 ` [GOODTITLE patch 3/8] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 169 Thomas Gleixner
2019-06-05 15:01 ` [GOODTITLE patch 4/8] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 293 Thomas Gleixner
2019-06-05 15:01 ` [GOODTITLE patch 5/8] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 337 Thomas Gleixner
2019-06-05 15:01 ` [GOODTITLE patch 6/8] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 415 Thomas Gleixner
2019-06-05 15:01 ` [GOODTITLE patch 7/8] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 425 Thomas Gleixner
2019-06-05 15:01 ` [GOODTITLE patch 8/8] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 492 Thomas Gleixner
2019-06-08 20:38 ` [GOODTITLE patch 0/8] Deep review of the 'good title' disclaimer variant Allison Randal
2019-06-10 3:28 ` Richard Fontana [this message]
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='CAC1cPGzpco=JYfZSE0BrEOdk1EGMpa0DOpBypZYw+aSxj0FtxA@mail.gmail.com' \
--to=rfontana@redhat.com \
--cc=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).