public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Greg KH <greg@kroah.com>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
	hch@lst.de, linux-kernel@vger.kernel.org
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Thu, 17 Jun 2004 21:54:58 +0200	[thread overview]
Message-ID: <20040617195458.GA31338@lst.de> (raw)
In-Reply-To: <20040617180507.GA18134@kroah.com>

On Thu, Jun 17, 2004 at 11:05:08AM -0700, Greg KH wrote:
> On Thu, Jun 17, 2004 at 11:29:55PM -0700, Adam J. Richter wrote:
> > 	I believe that Greg Kroah-Hartmann said that the changes
> > should go into 2.5.  I'm still waiting, although I don't know if
> > I even have a copy of the user level helper code anymore.
> 
> No one ever sent me patches to do this during the 2.5 development
> series.  That's why nothing changed.

WAKE UP!

We have files in the kernel we can't distribute.  We have a copyright
holder in that particular area who told you to stop it.  I told you
it's not okay and I'm a major kernel copyright holder to.  Do Adam & me
need to ask the vendors and mirrors to take the kernel tarball down
first before you react?

In fact if I see no action in, let's say a week, I'll probably do
exactly that.


  reply	other threads:[~2004-06-17 19:55 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
2004-06-17 20:22     ` mdpoole
2004-06-17 18:05 ` Greg KH
2004-06-17 19:54   ` Christoph Hellwig [this message]
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=20040617195458.GA31338@lst.de \
    --to=hch@lst.de \
    --cc=adam@yggdrasil.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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