Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752898Ab3ESOJP (ORCPT ); Sun, 19 May 2013 10:09:15 -0400 Received: from atl.turmel.org ([74.117.157.138]:60753 "EHLO atl.turmel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752262Ab3ESOJO (ORCPT ); Sun, 19 May 2013 10:09:14 -0400 X-Greylist: delayed 942 seconds by postgrey-1.27 at vger.kernel.org; Sun, 19 May 2013 10:09:14 EDT Message-ID: <5198D956.6010402@turmel.org> Date: Sun, 19 May 2013 09:53:26 -0400 From: Phil Turmel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130414 Thunderbird/17.0.5 MIME-Version: 1.0 To: "luke.leighton" CC: Ian Stirling , legal@lists.gpl-violations.org, Linux Kernel Mailing List Subject: Re: Would like to form a pool of Linux copyright holders for faster GPL enforcement against Anthrax Kernels References: <51972CAF.3060802@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1815 Lines: 42 On 05/19/2013 06:57 AM, luke.leighton wrote: > On Sun, May 19, 2013 at 10:12 AM, Ian Stirling 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/