public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Flavio Stanchina <flavio@stanchina.net>
To: mdpoole@troilus.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Thu, 17 Jun 2004 23:45:40 +0200	[thread overview]
Message-ID: <40D21104.5000802@stanchina.net> (raw)
In-Reply-To: <877ju5yjxp.fsf@sanosuke.troilus.org>

mdpoole@troilus.org wrote:
> Sure there is: To the extent that there is a real license problem,
> work with the copyright owner(s) for the files and binary blobs to
> resolve the problem.  [...]

Yes, of course that would be fine. I started with the implicit 
assumption that the license could not change, sorry.

This might open another can of worms however. Once you get a binary blob 
into the kernel and you know that it really is code for an embedded 
microprocessor or such, what is the "preferred form of the work for
making modifications to it"? Wouldn't that be source code in whatever 
language that blob is written in? Wouldn't that also require a toolchain 
to build it? MY opinion is that it' much better to get it out of the 
kernel anyway.

> Contrary to your (and SCO's) allegations, kernel gatekeepers
> generally exercise care with respect to new contributions.

I did not allege anything like that. I never doubted that Linus and most 
other maintainers do, in fact, understand legal things quite well, 
contrary to what SCO said or implied several times.

-- 
Ciao, Flavio


  parent reply	other threads:[~2004-06-17 21:37 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18  6:29 more files with licenses that aren't GPL-compatible 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 [this message]
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
  -- 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-16 23:47 Wichmann, Mats D
2004-06-17  1:18 ` Kyle Moffett
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=40D21104.5000802@stanchina.net \
    --to=flavio@stanchina.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdpoole@troilus.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