From: vsnsdualce@memeware.net
To: linux-kernel@vger.kernel.org, misc@openbsd.org,
gentoo-user@lists.gentoo.org
Cc: debian-user@lists.debian.org, ci-users@centos.org, centos@centos.org
Subject: Re: Thank you for your messages, and Happy New Year ;)
Date: Tue, 01 Jan 2019 23:30:48 +0000 [thread overview]
Message-ID: <b8e7b7bdaada30dfd719c7938ed5dc15@memeware.net> (raw)
In-Reply-To: <CAAaskFBmER_jHyiXyH=yM-0fObGy0LGgo9OfQOmwZ-psaimS+w@mail.gmail.com>
Thanks for your response :).
Please Spread the word regarding the copyright-holders rights (remeber:
the
Linux kernel programmers did not sign over their copyrights, one of the
reasons Linux grew so quickly amongst developers where GNU very slowly
(The FSF will only include code where the copyright has been transferred
to it)), thus the various 1000s of linux programmers who didn't work
for a company all retain their property rights.
A license is just that: license (permission). It is not a transfer of
rights. These licenses that were given are non-exclusive (not to just
one entity) and are thus cannot be construed as transfers either.
It's simply permission to use property, same as if you allowed a
neighbor
to use an ax you owned (gave them license to use the ax).
If that neighbor went and then chopped an enemy to pieces with that ax,
limb by limb, joint by joint, applying burning cauterizing oil after
each dismemberment,
he cannot say "I will not give you back the ax, because I relied on
your lease, and thus used the ax in such a way as it would be
inconvenient
for me to return it to you".
The ax is still yours and you may tell your friend: give me my ax back
now
(this is you rescinding the license).
parent reply other threads:[~2019-01-01 23:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAAaskFBmER_jHyiXyH=yM-0fObGy0LGgo9OfQOmwZ-psaimS+w@mail.gmail.com>]
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=b8e7b7bdaada30dfd719c7938ed5dc15@memeware.net \
--to=vsnsdualce@memeware.net \
--cc=centos@centos.org \
--cc=ci-users@centos.org \
--cc=debian-user@lists.debian.org \
--cc=gentoo-user@lists.gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=misc@openbsd.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