public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Tim Schmielau <tim@physik3.uni-rostock.de>,
	Fruhwirth Clemens <clemens@endorphin.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	James Morris <jmorris@redhat.com>
Subject: Re: GPL version, "at your option"?
Date: Wed, 17 Nov 2004 16:16:30 +0000	[thread overview]
Message-ID: <1100708189.512.64.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0411170822200.2222@ppc970.osdl.org>

On Mer, 2004-11-17 at 16:28, Linus Torvalds wrote:
> In other words, if you didn't have that "v2 or later" in your original 
> patches, they were _always_ just the regular GPLv2.

I did have that.

> That said, when I clarified (and I do want to make clear that the header 
> on the COPYING file is a _clarification_, not a change of license) it, I 
> told people that if they disagreed with me, they should send in patches 
> saying "v2 or later" to their own code.

Well no obligation exists, but please add "All code owned by Alan Cox
and present in this kernel is licensed GPL v2 or later" to your copying
or another appropriate file. (A comment in the code for each one would
be rather messy)

It might be a good idea to figure out how to have a list of contributors
who've said that or "v2 - or if Linus Torvalds so chooses, a later
version"

> Note the "IF". Linux _never_ had the "v2 or later" clause, so that "if" 
> was never an issue, and the clarification on top of the COPYING file 
> really _is_ just a clarification.

Correction noted. I went and checked 1.2.0 and indeed it says nothing
about versions in that specific top level file.

Alan


  reply	other threads:[~2004-11-17 17:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 14:08 GPL version, "at your option"? Fruhwirth Clemens
2004-11-16 14:35 ` Erik Mouw
2004-11-16 14:58   ` Fruhwirth Clemens
2004-11-16 14:40 ` Charles Cazabon
2004-11-17 15:07   ` Alan Cox
2004-11-17 16:33     ` Michael Poole
2004-11-17 16:09       ` Alan Cox
2004-11-16 14:48 ` Tim Schmielau
2004-11-16 15:46   ` Linus Torvalds
2004-11-17 15:09     ` Alan Cox
2004-11-17 16:28       ` Linus Torvalds
2004-11-17 16:16         ` Alan Cox [this message]
2004-11-17 17:59           ` Linus Torvalds
2004-11-17 21:11           ` Jesper Juhl
2004-11-16 15:38 ` James Morris
2004-11-18  1:04 ` David Schwartz
2004-11-18  2:12   ` Kyle Moffett
2004-11-18  2:50     ` Dmitry Torokhov
2004-11-18  3:11       ` Kyle Moffett
2004-11-18  4:54         ` Dmitry Torokhov
2004-11-18 15:46         ` David Schwartz

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=1100708189.512.64.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=clemens@endorphin.org \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@physik3.uni-rostock.de \
    --cc=torvalds@osdl.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