From: Phil Turmel <philip@turmel.org>
To: "luke.leighton" <luke.leighton@gmail.com>
Cc: Ian Stirling <gplvio@mauve.plus.com>,
legal@lists.gpl-violations.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Would like to form a pool of Linux copyright holders for faster GPL enforcement against Anthrax Kernels
Date: Sun, 19 May 2013 09:53:26 -0400 [thread overview]
Message-ID: <5198D956.6010402@turmel.org> (raw)
In-Reply-To: <CAPweEDztcCOgKQmMSK3R6TMJoOo5m4b5KFg1nVySexqdVZu_DQ@mail.gmail.com>
On 05/19/2013 06:57 AM, luke.leighton wrote:
> On Sun, May 19, 2013 at 10:12 AM, Ian Stirling <gplvio@mauve.plus.com> wrote:
>> On 18.05.2013 19:27, luke.leighton wrote:
>>
>>> question: what is the procedure for having that licensing explicitly
>>> added to the linux kernel sources?
[snip license compatibility argument /]
> i don't give a fuck about what anybody else may choose; i do not give
> a fuck about the timescales. i want *MY* choice to be respected: *MY*
> code contributions under the GPLv2 and GPLv3+ and have that properly
> recorded.
You seem to be under some misunderstanding about the kernel community's
obligations to you. Their only obligation is to respect your copyright
as you submitted your changes. (Signed-off-by === GPLv2 compatible).
The GPL is designed for its provisions to take effect at the point of
distribution.
Each contributor is choosing to publish/distribute through Linus. Linus
chooses to publish/distribute via kernel.org under the trademarked name
"Linux". Most distributions publish their own kernels, but choose to
base them on Linus' kernel for economies of scale.
If you don't like what any of the above choose to publish/distribute,
you may publish/distribute the code yourself, provided you respect the
other contributors' licenses.
> so. could someone please inform me what the procedure is: is it as
> simple as submitting a patch?
You can submit a patch. The kernel community is not obligated to accept
it. If you want to be sure your license choice is "properly recorded",
publish it yourself.
Phil
next prev parent reply other threads:[~2013-05-19 14:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 7:24 Would like to form a pool of Linux copyright holders for faster GPL enforcement against Anthrax Kernels Eric Appleman
2013-05-18 8:28 ` Eric Appleman
2013-05-18 18:27 ` luke.leighton
[not found] ` <1368918189923.dd7325ed@Nodemailer>
2013-05-19 10:39 ` luke.leighton
2013-05-19 11:04 ` Ralph Corderoy
2013-05-19 12:24 ` luke.leighton
2013-05-19 18:01 ` Thomas Charron
2013-05-19 11:19 ` Jonas Gorski
2013-05-19 12:34 ` luke.leighton
2013-05-19 13:28 ` Jonas Gorski
2013-05-19 13:45 ` Theodore Ts'o
2013-05-19 18:06 ` Thomas Charron
2013-05-19 17:55 ` Thomas Charron
[not found] ` <ce644e6e12d68aaabed7403b5f21c124@imap.plus.net>
2013-05-19 10:57 ` luke.leighton
2013-05-19 13:53 ` Phil Turmel [this message]
2013-05-20 10:24 ` Ian Stirling
2013-05-20 11:33 ` Theodore Ts'o
2013-05-22 16:13 ` Denis 'GNUtoo' Carikli
2013-05-22 17:56 ` Theodore Ts'o
2013-05-21 10:11 ` Rob Landley
2013-05-22 15:45 ` Denis 'GNUtoo' Carikli
2013-05-22 15:59 ` Denis 'GNUtoo' Carikli
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=5198D956.6010402@turmel.org \
--to=philip@turmel.org \
--cc=gplvio@mauve.plus.com \
--cc=legal@lists.gpl-violations.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.leighton@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