From: Christoph Hellwig <hch@infradead.org>
To: Chris Abbey <linux@cabbey.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: possible GPL violation involving linux kernel code
Date: Sun, 21 Apr 2002 12:17:32 +0100 [thread overview]
Message-ID: <20020421121732.A16765@infradead.org> (raw)
In-Reply-To: <20020421074858.A8318@infradead.org> <Pine.LNX.4.33.0204210147550.26531-100000@tweedle.cabbey.net>
On Sun, Apr 21, 2002 at 01:52:34AM -0500, Chris Abbey wrote:
> Today, Christoph Hellwig wrote:
> > Calm down
>
> I am calm. As I said, I didn't want to post it, but that's the
> best way to get word to the copyright holders, who are the only
> ones that can act on any violations.
Blah. First thing you'd do if you were serious would be to contact
Promise. If they have a support person that has a little more clue
than their driver guys they'd point you to the OpenLinux kernel source
RPM and you wouldn't even have to make so much noise.
>
> > - OpenLinux driver disks are supposed to contain the standard
> > modules in addition to the new ones. You can find your sources in
> > /usr/src/linux.
>
> Not on that floppy you don't, nor in the download that included the
> floppy image, nor in any offer contained within that disk/image, nor
> on promise's website along with that image.
Where the heck did you get the impression from that this is required by
the GPL?
Christoph
--
Dont't feed the trolls.
next prev parent reply other threads:[~2002-04-21 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 6:43 possible GPL violation involving linux kernel code Chris Abbey
2002-04-21 6:48 ` Christoph Hellwig
2002-04-21 6:52 ` Chris Abbey
2002-04-21 11:17 ` Christoph Hellwig [this message]
2002-04-21 14:10 ` Eric W. Biederman
2002-04-22 18:42 ` Doug Ledford
2002-04-21 20:14 ` Chris Abbey
2002-04-21 20:54 ` Sean Neakums
2002-04-22 0:05 ` Pavel Machek
2002-04-21 17:27 ` Sean Neakums
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=20020421121732.A16765@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@cabbey.net \
/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