From: <Hell.Surfers@cwctv.net>
To: alan@lxorguk.ukuu.org.uk, paul@clubi.ie, riel@conectiva.com.br,
linux-kernel@vger.kernel.org, rms@gnu.org
Subject: RE:Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Thu, 2 Jan 2003 05:37:40 +0000 [thread overview]
Message-ID: <0f0fb5934050213DTVMAIL12@smtp.cwctv.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
"or later" perhaps copyright could be defined, and headers added to derivative?
Dean. Three ways to kill yourself, and ive been drove in one...
On 02 Jan 2003 01:57:01 +0000 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
[-- Attachment #2: Type: message/rfc822, Size: 1667 bytes --]
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Paul Jakma <paul@clubi.ie>
Cc: Rik van Riel <riel@conectiva.com.br>, Hell.Surfers@cwctv.net, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, rms@gnu.org
Subject: Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: 02 Jan 2003 01:57:01 +0000
Message-ID: <1041472621.22606.4.camel@irongate.swansea.linux.org.uk>
On Thu, 2003-01-02 at 00:31, Paul Jakma wrote:
> So I am not quite sure on what basis one could argue the NVidia
> driver is not a derivative work, and hence it seems to me the NVidia
> driver is technically in material breach of GPL.
I would assume Nvidia's view is based on US caselaw on what constitutes
a 'derived work'. The boundaries of copyright are not set by the GPL
authors
next reply other threads:[~2003-01-02 5:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 5:37 Hell.Surfers [this message]
2003-01-02 21:42 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2003-01-08 16:26 Hell.Surfers
2003-01-05 6:14 Hell.Surfers
2003-01-02 17:39 Hell.Surfers
2003-01-02 6:25 Hell.Surfers
2003-01-02 6:16 Hell.Surfers
2003-01-02 6:14 Hell.Surfers
2003-01-02 6:04 Hell.Surfers
2003-01-02 5:33 Hell.Surfers
2003-01-03 13:02 ` NEURONET
2003-01-01 18:10 Hell.Surfers
2003-01-01 5:51 Hell.Surfers
2003-01-01 5:46 ` David Lang
2003-01-01 7:43 ` Andre Hedrick
2003-01-01 5:45 RE:Re: " Hell.Surfers
2003-01-01 5:55 ` A Guy Called Tyketto
2003-01-01 5:30 Hell.Surfers
2003-01-01 5:51 ` A Guy Called Tyketto
2003-01-01 5:08 Hell.Surfers
2003-01-01 5:01 Hell.Surfers
2003-01-01 1:51 Hell.Surfers
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=0f0fb5934050213DTVMAIL12@smtp.cwctv.net \
--to=hell.surfers@cwctv.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@clubi.ie \
--cc=riel@conectiva.com.br \
--cc=rms@gnu.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
all inboxes | Powered by JetHome®