From: jlnance@unity.ncsu.edu
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Did the SCO Group plant UnixWare source in the Linux kernel?
Date: Fri, 2 May 2003 08:57:35 -0400 [thread overview]
Message-ID: <20030502125735.GA3409@ncsu.edu> (raw)
In-Reply-To: <20030502064349.A9988@infradead.org>
On Fri, May 02, 2003 at 06:43:49AM +0100, Christoph Hellwig wrote:
> It might be more interesting to look for stolen Linux code in Unixware,
> I'd suggest with the support for a very well known Linux fileystem in
> the Linux compat addon product for UnixWare..
Wouldnt it be halirous if whatever code SCO is talking about when they
say there is Unix code in Linux turns out to be code some SCO employee
ripped out of some GPL program and stuck it into Unixware. That is
actually far more likely than what they alledge.
Jim
next prev parent reply other threads:[~2003-05-02 12:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 3:21 Did the SCO Group plant UnixWare source in the Linux kernel? The Spirit of Open Source
2003-05-02 4:28 ` Chris Friesen
2003-05-02 5:43 ` Christoph Hellwig
2003-05-02 12:57 ` jlnance [this message]
2003-05-03 2:10 ` jw schultz
2003-05-03 4:26 ` Daniel Phillips
2003-05-02 15:53 ` Carl-Daniel Hailfinger
2003-05-02 16:38 ` John Jasen
2003-05-02 17:20 ` Carl-Daniel Hailfinger
2003-05-02 17:28 ` John Jasen
2003-05-02 17:43 ` Carl-Daniel Hailfinger
[not found] <fa.gqa0utv.1i0gigr@ifi.uio.no>
2003-05-02 12:40 ` Nomen Nescio
2003-05-02 14:02 ` Chris Friesen
-- strict thread matches above, loose matches on Subject: below --
2003-05-02 14:06 Ben Collins
2003-05-02 15:00 ` Balram Adlakha
2003-05-02 15:11 ` Richard B. Johnson
2003-05-02 14:57 Downing, Thomas
2003-05-02 15:14 ` Richard B. Johnson
2003-05-02 15:23 Downing, Thomas
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=20030502125735.GA3409@ncsu.edu \
--to=jlnance@unity.ncsu.edu \
--cc=hch@infradead.org \
--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