From: "Jeff V. Merkey" <jmerkey@drdos.com>
To: Rik van Riel <riel@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
jonathan@jonmasters.org,
"jmerkey@comcast.net" <jmerkey@comcast.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Possible GPL Violation of Linux in Amstrad's E3 Videophone
Date: Thu, 07 Oct 2004 15:16:02 -0600 [thread overview]
Message-ID: <4165B212.1070602@drdos.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0410071706220.18453-100000@chimarrao.boston.redhat.com>
Rik van Riel wrote:
>On Thu, 7 Oct 2004, Jeff V. Merkey wrote:
>
>
>
>>We offer to kernel.org the sum of $50,000.00 US for a one time
>>license to the Linux Kernel Source for a single snapshot of
>>a single Linux version by release number.
>>
>>
>
>That would still be useless, since it doesn't give you any
>rights to the (GPL) bug fixes posted to this list on an
>almost daily basis.
>
>
>
Obviously, what would happen here is a release of 2.4 or 2.6 that is
stable would be snapshoted
and used. And yes, you are correct, bug fixes would not be allowed
unless they were applied
independently and without access to GPL code. However, this would allow
OSDL and kernel.org
to become self-sustaining and would not impact the GPL process -- just
let you guys peel
off releases and pocket some $$$ on the side. A lot of big companies
would line up to pay you.
So, who do I write the check to?
Jeff
next prev parent reply other threads:[~2004-10-07 21:57 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 17:40 Possible GPL Violation of Linux in Amstrad's E3 Videophone jmerkey
2004-10-01 18:23 ` Jesse Pollard
2004-10-01 19:34 ` Valdis.Kletnieks
2004-10-01 19:46 ` Jeff V. Merkey
2004-10-01 20:38 ` Geert Uytterhoeven
2004-10-01 20:40 ` Valdis.Kletnieks
2004-10-01 22:09 ` Jon Masters
2004-10-01 21:53 ` Jeff V. Merkey
2004-10-01 23:51 ` Michael Poole
2004-10-02 2:00 ` Theodore Ts'o
[not found] ` <20041002064620.GA8568@galt.devicelogics.com>
2004-10-02 10:27 ` Jon Masters
2004-10-02 17:34 ` Alan Cox
2004-10-03 11:46 ` Willy Tarreau
2004-10-03 11:59 ` Jon Masters
2004-10-03 22:01 ` Alan Cox
2004-10-04 0:23 ` Kyle Moffett
2004-10-07 19:21 ` Jeff V. Merkey
2004-10-07 20:24 ` Chris Friesen
2004-10-07 21:22 ` Jeff V. Merkey
2004-10-07 22:32 ` Chris Friesen
2004-10-07 22:57 ` Hua Zhong
2004-10-08 8:19 ` Henning P. Schmiedehausen
2004-10-07 21:07 ` Rik van Riel
2004-10-07 21:16 ` Jeff V. Merkey [this message]
2004-10-07 21:40 ` Kyle Moffett
2004-10-07 21:17 ` Jeff V. Merkey
2004-10-07 22:02 ` Kyle Moffett
2004-10-07 21:29 ` Jeff V. Merkey
2004-10-08 12:27 ` Ingo Molnar
2004-10-08 18:24 ` Geert Uytterhoeven
2004-10-08 18:42 ` Ingo Molnar
2004-10-09 9:50 ` James Courtier-Dutton
2004-10-08 12:16 ` Alan Cox
2004-10-07 22:18 ` Dave Jones
2004-10-07 21:51 ` Jeff V. Merkey
2004-10-07 22:41 ` Dave Jones
2004-10-08 0:47 ` Jeff Garzik
2004-10-07 23:50 ` viro
2004-10-08 0:40 ` Jesper Juhl
2004-10-08 0:59 ` Jon Masters
[not found] ` <20041008032034.GD3528@galt.devicelogics.com>
2004-10-08 7:15 ` Jon Masters
2004-10-08 12:38 ` Gene Heskett
2004-10-08 12:50 ` Gene Heskett
2004-10-08 13:48 ` Bruce Ferrell
2004-10-08 15:14 ` Gene Heskett
2004-10-08 2:48 ` Erik Andersen
2004-10-10 6:35 ` Brian Litzinger
2004-10-10 13:25 ` Alan Cox
2004-10-10 22:26 ` Jon Masters
2004-10-11 11:57 ` Tonnerre
2004-10-08 2:40 ` Erik Andersen
2004-10-08 8:50 ` Bernd Petrovitsch
2004-10-08 11:08 ` William Lee Irwin III
2004-10-04 20:26 ` Jesse Pollard
2004-10-02 12:35 ` James Courtier-Dutton
2004-10-04 18:03 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-09-29 13:44 Ralph Corderoy
2004-10-01 14:52 ` Denis Vlasenko
2004-10-01 14:20 ` Alan Cox
2004-10-01 15:59 ` Ralph Corderoy
2004-10-01 16:00 ` Alan Cox
2004-10-01 16:24 ` Jon Masters
2004-10-01 15:59 ` Alan Cox
2004-10-01 17:18 ` Jon Masters
2005-01-07 21:48 ` Jonathan McDowell
2005-01-15 13:43 ` Jonathan McDowell
2005-01-26 16:47 ` Jonathan McDowell
2004-10-01 17:24 ` Tigran Aivazian
2004-10-01 16:14 ` James Courtier-Dutton
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=4165B212.1070602@drdos.com \
--to=jmerkey@drdos.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jmerkey@comcast.net \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).