From: Ian Stirling <gplvio@mauve.plus.com>
To: "luke.leighton" <luke.leighton@gmail.com>
Cc: <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: Mon, 20 May 2013 11:24:02 +0100 [thread overview]
Message-ID: <18adac813097459e346581e2d81389be@imap.plus.net> (raw)
In-Reply-To: <CAPweEDztcCOgKQmMSK3R6TMJoOo5m4b5KFg1nVySexqdVZu_DQ@mail.gmail.com>
On 19.05.2013 11:57, 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?
>>
>>
>> Fork the kernel, and put it up on a repo somewhere that says you're
>> trying
>> to get it all as
>> GPL3.
<snip>
>
> i wish to know the procedure by which my formally and publicly
> announced release of all linux kernel contributions under the dual
> licenses of GPLv2 and GPLv3+ may be entered - formally - upstream and
> into the linux kernel sources being maintained on git.kernel.org
Umm - that was my point - though I did not make it explicitly.
Either there is a policy change, and it is decided to allow such
dual-licenced code in the repo, or your code does not get checked in,
as it does not have a compatible licence.
If Linus takes the view that he does not wish to allow this - and the
project is not forked - you actually have to do the above.
Sure - you have the right to licence code you write any way you choose.
Linus (and the people involved in maintaining the kernel) have the
right
to not accept your code under that licence.
next prev parent reply other threads:[~2013-05-20 10:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 7:24 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
2013-05-20 10:24 ` Ian Stirling [this message]
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=18adac813097459e346581e2d81389be@imap.plus.net \
--to=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
Powered by JetHome