From: "Theodore Ts'o" <tytso@mit.edu>
To: "Denis 'GNUtoo' Carikli" <GNUtoo@no-log.org>
Cc: "luke.leighton" <luke.leighton@gmail.com>,
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: Wed, 22 May 2013 13:56:17 -0400 [thread overview]
Message-ID: <20130522175617.GA20848@thunk.org> (raw)
In-Reply-To: <20130522181329.234f43f0@m4a785t-m.lan>
On Wed, May 22, 2013 at 06:13:29PM +0200, Denis 'GNUtoo' Carikli wrote:
> On Sun, 19 May 2013 11:57:15 +0100 "luke.leighton" <luke.leighton@gmail.com> wrote:
> > so. could someone please inform me what the procedure is: is it as
> > simple as submitting a patch?
> I think so(however I'm not a kernel maintainer),
> I found that(however the patch is really old):
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=798b6b19d7a4b6e1ea5340ec8b3b92811e05b81b
> So the idea would be to send a patch or series of patches to relicense
> your code under the GPLv2+(GPLv2 or later).
Only if you own the copyright on all of the lines of code of the file
in question.
- Ted
next prev parent reply other threads:[~2013-05-22 17:56 UTC|newest]
Thread overview: 26+ 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
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 [this message]
2013-05-21 10:11 ` Rob Landley
2013-05-22 15:45 ` Denis 'GNUtoo' Carikli
2013-05-22 15:59 ` Denis 'GNUtoo' Carikli
-- strict thread matches above, loose matches on Subject: below --
2013-05-18 8:21 Eric Appleman
2013-05-18 8:26 Eric Appleman
2013-05-20 15:13 ` Bradley M. Kuhn
2013-05-20 15:13 ` Bradley M. Kuhn
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=20130522175617.GA20848@thunk.org \
--to=tytso@mit.edu \
--cc=GNUtoo@no-log.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.