From: Adrian Bunk <bunk@fs.tum.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Promise SATA driver GPL'd
Date: Wed, 23 Jul 2003 12:37:45 +0200 [thread overview]
Message-ID: <20030723103745.GA26422@fs.tum.de> (raw)
In-Reply-To: <20030723101228.GC4172@merlin.emma.line.org>
On Wed, Jul 23, 2003 at 12:12:28PM +0200, Matthias Andree wrote:
> On Wed, 23 Jul 2003, Adrian Bunk wrote:
>
> > There are _many_ people that have a copyright on parts of the Linux
> > kernel (the exact number might be different in different countries due
> > to different copyright laws). To change the copyright to anything other
> > than GPL v2 is practically impossible (even if a new version of the GPL
> > might fix the deficits you mentioned).
>
> How about the "or, at your option, any later version" clause in the GPL?
This clause is not part of the GPL, it's only a suggestion on how to
copyright your code.
COPYING in the kernel sources includes an explict statement.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-07-23 10:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 5:12 Promise SATA driver GPL'd Adam J. Richter
2003-07-23 5:28 ` Andre Hedrick
2003-07-23 9:08 ` Adrian Bunk
2003-07-23 10:12 ` Matthias Andree
2003-07-23 10:21 ` Wichert Akkerman
2003-07-23 11:47 ` Alan Cox
2003-07-23 11:54 ` Wichert Akkerman
2003-07-23 22:22 ` On "any later version" in GPL [Was: Re: Promise SATA driver GPL'd] Horst von Brand
2003-07-23 10:37 ` Adrian Bunk [this message]
2003-07-23 10:29 ` Promise SATA driver GPL'd Alan Cox
2003-07-23 10:51 ` Adrian Bunk
2003-07-23 11:43 ` Alan Cox
2003-07-23 12:17 ` Adrian Bunk
2003-07-23 12:32 ` Martin Diehl
2003-07-23 12:57 ` Alan Cox
2003-07-23 19:08 ` Andre Hedrick
2003-07-23 19:19 ` Alan Cox
2003-07-23 19:33 ` Andre Hedrick
2003-07-23 19:46 ` Andre Hedrick
2003-07-23 20:59 ` Roman Zippel
2003-07-23 22:22 ` Andre Hedrick
2003-07-23 22:40 ` Roman Zippel
2003-07-23 22:35 ` Andre Hedrick
2003-07-23 23:02 ` Roman Zippel
2003-07-23 23:08 ` Andre Hedrick
2003-07-23 23:33 ` Roman Zippel
2003-07-23 23:45 ` Andre Hedrick
2003-07-24 0:14 ` dacin
2003-07-24 0:23 ` Andre Hedrick
2003-07-24 0:21 ` David Schwartz
2003-07-24 0:21 ` Andre Hedrick
2003-07-24 13:23 ` Jesse Pollard
2003-07-24 14:01 ` Richard B. Johnson
2003-07-24 18:37 ` David Schwartz
2003-07-23 22:32 ` Andre Hedrick
2003-07-23 22:46 ` Larry McVoy
2003-07-23 23:13 ` Roman Zippel
2003-07-23 10:40 ` Adam Sampson
-- strict thread matches above, loose matches on Subject: below --
2003-07-22 18:45 Erik Andersen
2003-07-22 18:54 ` Jeff Garzik
2003-07-22 19:07 ` Erik Andersen
2003-07-22 19:39 ` Samuel Flory
2003-07-22 20:56 ` Jeff Garzik
2003-07-22 21:39 ` Erik Andersen
2003-07-22 23:25 ` Jeff Garzik
2003-08-27 3:01 ` Nick Urbanik
2003-08-27 3:14 ` Jeff Garzik
2003-08-27 9:00 ` Matthias Andree
2003-08-27 11:51 ` Jeff Garzik
2003-07-22 20:57 ` Jeff Garzik
2003-07-23 13:20 ` Mark Watts
2003-07-23 1:59 ` Andre Hedrick
2003-07-23 2:38 ` Shawn
2003-07-23 10:32 ` Alan Cox
2003-07-23 18:58 ` Andre Hedrick
2003-07-24 11:22 ` Matthias Andree
2003-08-13 13:34 ` Vojtech Pavlik
2003-08-13 14:24 ` Jeff Garzik
2003-08-15 10:17 ` Andre Hedrick
2003-07-25 3:44 ` Milan Roubal
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=20030723103745.GA26422@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.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