From: vnsndalce@memeware.net
To: linux-kernel@vger.kernel.org, debian-user@lists.debian.org,
legal@lists.fedoraproject.org, users@lists.fedoraproject.org,
rms@gnu.org
Cc: gentoo-user@lists.gentoo.org, ubuntu-users@lists.ubuntu.com,
misc@openbsd.org
Subject: Without an attached interest you can very well revoke the license and prevent all further distribution of your code, and further use of it in future versions.
Date: Tue, 01 Jan 2019 20:03:26 +0000 [thread overview]
Message-ID: <5ff2d769e29faad86bab566335820a29@memeware.net> (raw)
> The GPL is not revocable despite not being a contract. It is a license
> to distribute software and you cannot revoke the license on already
> existing publications. All you can do is revoke the license on future
> publications.
>> 1014527
Without an attached interest you can very well revoke the license and
prevent all further distribution of your code, and further use of it in
future versions.
You can revoke the license.
What you are thinking about is the normal case of commercial
distribution licenses - which have an attached interest (they were paid
for, the licensor received consideration).
Almost all court cases involve such issues. Not bare licenses.
Additionally you are thinking about consumer protection statutes that
would run against the property owner successfully suing for the
destruction of all current now-unlicensed copies in existence.
Once the license is revoked the linux team may no-longer use the revoked
code in future versions. They no longer have permission - the license
they were given ceases to exist.
Normally the copyright owner then has the option to pray to the court
that all unlicensed copys be destroyed. The court, as you put, is
unlikely to grant this form of relief regarding existing copys that
existed prior to the revocation.
That does not mean that Linux Team still is licensed to modify or
distribute the code: they are not. The license does not survive the
revocation.
reply other threads:[~2019-01-01 20:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5ff2d769e29faad86bab566335820a29@memeware.net \
--to=vnsndalce@memeware.net \
--cc=debian-user@lists.debian.org \
--cc=gentoo-user@lists.gentoo.org \
--cc=legal@lists.fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=misc@openbsd.org \
--cc=rms@gnu.org \
--cc=ubuntu-users@lists.ubuntu.com \
--cc=users@lists.fedoraproject.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
Powered by JetHome