From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Pavel Nikulin <nikulinpi@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy
Date: Fri, 20 Oct 2017 19:25:37 +0100 [thread overview]
Message-ID: <20171020192519.78772151@alans-desktop> (raw)
In-Reply-To: <CAN3U_kVTaRRW3kkSBb8Ko8NQwgkQGv3_BgfWXq1mw_1R1h4_Uw@mail.gmail.com>
On Thu, 19 Oct 2017 18:28:12 +0300
Pavel Nikulin <nikulinpi@gmail.com> wrote:
> Hold!
>
> Greg, are you trying to put a new addendum to the terms of GPL v2?
In many parts of the world if you make a promise about not enforcing a
right to take some action (sometimes even an implied one) you cannot then
take that action.
So if you say "I won't sue you just because you've got a tiny GPL
compliance issue", then in much of the world if you attempt to do so
you'll find you can't.
I do think it's poorly drafted because it doesn't contain any "unless you
sue us" caveat so you won't find my name on it.
Alan
next prev parent reply other threads:[~2017-10-20 18:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 15:28 [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy Pavel Nikulin
2017-10-20 7:29 ` Greg KH
2017-10-20 18:25 ` Alan Cox [this message]
2017-10-21 8:03 ` Greg KH
2017-10-21 19:16 ` Pavel Nikulin
2017-10-22 2:28 ` Bradley M. Kuhn
2017-10-23 7:50 ` Greg KH
2017-10-23 13:11 ` Pavel Nikulin
2017-10-23 14:35 ` Theodore Ts'o
2017-10-23 17:47 ` Damian Tometzki
2017-10-23 18:26 ` Damian Tometzki
-- strict thread matches above, loose matches on Subject: below --
2017-10-16 9:25 Greg KH
2017-10-16 13:11 ` David Woodhouse
2017-10-16 13:46 ` Greg KH
2017-10-16 14:31 ` Bradley M. Kuhn
2017-10-16 14:50 ` David Woodhouse
2017-10-17 14:57 ` Greg KH
2017-12-10 8:21 ` Pavel Machek
2017-10-17 8:06 ` Greg KH
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=20171020192519.78772151@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikulinpi@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