From: Kyle Moffett <mrmacman_g4@mac.com>
To: "Wichmann, Mats D" <mats.d.wichmann@intel.com>
Cc: eric@cisu.net, davids@webmaster.com,
linux-kernel@vger.kernel.org,
Erik Harrison <erikharrison@gmail.com>
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Wed, 16 Jun 2004 21:18:05 -0400 [thread overview]
Message-ID: <2F53409E-BFFC-11D8-8574-000393ACC76E@mac.com> (raw)
In-Reply-To: <A06801158AE07847B27A52C1A074BC1D04C910B4@fmsmsx404.amr.corp.intel.com>
On Jun 16, 2004, at 19:47, Wichmann, Mats D wrote:
> Please keep distinct "ship with" in the sense of /inside/ the
> kernel and "ship with" in the sense of on the same distribution
> media. The GPL also has explicit wording for the latter
> (you've already been quoted the words on the former):
Well the firmware is compiled to bytes within the _same_file_ as
the rest of the kernel. That would match the usage of "inside" the
kernel. Even if it's just a file with firmware bytes distributed in the
same tar file it's still very iffy.
> "In addition, mere aggregation of another work not based on the
> Program with the Program (or with a work based on the Program)
> on a volume of a storage or distribution medium does not bring
> the other work under the scope of this License. "
But we're not talking about an instance of aggregation here, this
is a derivative work.
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2004-06-17 1:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 23:47 Wichmann, Mats D
2004-06-17 1:18 ` Kyle Moffett [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 6:56 Adam J. Richter
2004-06-18 11:09 ` mdpoole
2004-06-18 6:29 Adam J. Richter
2004-06-17 15:44 ` Michael Poole
2004-06-17 17:09 ` Adam J. Richter
2004-06-17 19:14 ` Kyle Moffett
2004-06-17 20:51 ` Flavio Stanchina
2004-06-17 20:53 ` Kyle Moffett
2004-06-17 21:05 ` mdpoole
2004-06-17 21:10 ` Christoph Hellwig
2004-06-17 21:45 ` Flavio Stanchina
2004-06-17 20:22 ` mdpoole
2004-06-17 18:05 ` Greg KH
2004-06-17 19:54 ` Christoph Hellwig
2004-06-17 20:22 ` Greg KH
2004-06-17 20:30 ` Christoph Hellwig
2004-06-17 20:52 ` Greg KH
2004-06-15 20:57 Christoph Hellwig
2004-06-16 0:38 ` Eric
2004-06-16 1:27 ` Kyle Moffett
2004-06-16 4:11 ` David Schwartz
2004-06-16 20:34 ` Erik Harrison
2004-06-16 20:37 ` Christoph Hellwig
2004-06-16 21:21 ` David Schwartz
2004-06-16 22:45 ` Oliver Neukum
2004-06-16 23:45 ` David Schwartz
2004-06-17 14:09 ` Timothy Miller
2004-06-17 18:35 ` David Schwartz
2004-06-17 19:22 ` Timothy Miller
2004-06-17 7:59 ` Christoph Hellwig
2004-06-17 8:43 ` Oliver Neukum
2004-06-17 8:47 ` Christoph Hellwig
2004-06-17 10:09 ` Martin Diehl
2004-06-17 10:14 ` Christoph Hellwig
2004-06-19 18:29 ` David Woodhouse
2004-06-17 14:04 ` Timothy Miller
2004-06-16 22:49 ` Helge Hafting
2004-06-18 9:08 ` Adrian Cox
2004-06-18 11:21 ` Kyle Moffett
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=2F53409E-BFFC-11D8-8574-000393ACC76E@mac.com \
--to=mrmacman_g4@mac.com \
--cc=davids@webmaster.com \
--cc=eric@cisu.net \
--cc=erikharrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mats.d.wichmann@intel.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®