From: Andre Hedrick <andre@linux-ide.org>
To: A Guy Called Tyketto <tyketto@wizard.com>
Cc: Hell.Surfers@cwctv.net, linux-kernel@vger.kernel.org
Subject: Re: Re: Why is Nvidia given GPL'd code to use in closed source drivers?
Date: Tue, 31 Dec 2002 23:21:43 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.10.10212312320060.421-100000@master.linux-ide.org> (raw)
In-Reply-To: <20030101051342.GA8365@wizard.com>
Tyketto !!!!
AMEN !!!!
Andre Hedrick
LAD Storage Consulting Group
On Tue, 31 Dec 2002, A Guy Called Tyketto wrote:
> First off, could you please your MUA to use 80 columns? having to
> manually put in carriage returns to read your mail gets rather tedious...
>
> On Wed, Jan 01, 2003 at 05:01:12AM +0000, Hell.Surfers@cwctv.net wrote:
<snip>
>
> I know why the GPL exists.. however, that does not mean or indicate
> that a company could not use the GPL for their own reasons. They a) wrote
> their own code, b) may have used headers that were GPL'ed, but does not mean
> or insinuate that just because they use GPL'd headers that they must have
> their SOURCE open. Many companies use GPL'd material, for their own purposes,
> and not have to have their own personal source open. You may want to read into
> the actual documentation for the GPL and LGPL.
>
> Besides.. Who is an honest contributor who worked on NVidia's own
> module? Did anyone outside NVidia write it? no. NVidia wrote it, NVidia
> released it, it's NVidia's IP. you're confusing Headers with the actual code.
>
> Like Snoop Dogg said. If you don't like it, don't buy it.
next prev parent reply other threads:[~2003-01-01 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 5:01 Hell.Surfers
2003-01-01 5:13 ` A Guy Called Tyketto
2003-01-01 7:21 ` Andre Hedrick [this message]
2003-01-01 7:40 ` jw schultz
2003-01-01 5:08 Hell.Surfers
2003-01-01 5:15 ` A Guy Called Tyketto
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=Pine.LNX.4.10.10212312320060.421-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=Hell.Surfers@cwctv.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tyketto@wizard.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
all inboxes | Powered by JetHome®