mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stuart Longland <stuartl@longlandclan.hopto.org>
To: Valdis.Kletnieks@vt.edu
Cc: bill davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: SCO's "proof"
Date: Thu, 21 Aug 2003 13:09:27 +1000	[thread overview]
Message-ID: <3F4437E7.2090307@longlandclan.hopto.org> (raw)
In-Reply-To: <200308201846.h7KIk6uu013871@turing-police.cc.vt.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Valdis.Kletnieks@vt.edu wrote:

| On Wed, 20 Aug 2003 18:27:31 -0000, davidsen@tmr.com (bill davidsen)
said:
|
|>Colin Paul Adams  <colin@colina.demon.co.uk> wrote:
|>| But Caldera are SCO now, aren't they? Are they going to sue themselves!?
|>
|>Thay should! Oh wait, you said sue, not shoot... nevermind.
|
|
| Only in the foot.. only in the foot.. unfortunately.

This case is getting more rediculous with each day...lfmao

Oh dear, it seems that our /comments/ are alike.  Hrmm.  Pity the
compiller doesn't take any notice of them, and therefore, I don't see
the evidence that the /code/ has been stolen.  Also, as others have
quite rightfully pointed out, it doesn't even compile -- syntax errors
galore.

Lets hope some people in the legal profession have some C knowledge --
or at least have the sense to go directly to the kernel source on
kernel.org rather than relying on what SCO provides.

- --
+-------------------------------------------------------------+
| Stuart Longland           stuartl at longlandclan.hopto.org |
| Brisbane Mesh Node: 719             http://stuartl.cjb.net/ |
| I haven't lost my mind - it's backed up on a tape somewhere |
| Griffith Student No:           Course: Bachelor/IT (Nathan) |
+-------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/RDfnIGJk7gLSDPcRAraOAJ9IEfQg1EsVTPXXg83ffjounKBheQCdH6D3
emz7olLrHtyrkSzR+kSS3Vk=
=h6EB
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-08-21  3:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 13:37 Brandon Stewart
2003-08-19 14:52 ` Dr. David Alan Gilbert
2003-08-19 15:01   ` Frank Gevaerts
2003-08-19 15:22     ` Tupshin Harper
2003-08-19 15:25     ` Colin Paul Adams
2003-08-19 20:46       ` Kurt Wall
2003-08-20 18:27       ` bill davidsen
2003-08-20 18:46         ` Valdis.Kletnieks
2003-08-21  3:09           ` Stuart Longland [this message]
2003-08-21 10:22             ` Stephan von Krawczynski
2003-08-19 15:07 ` Bart Samwel
2003-08-19 15:31   ` Richard B. Johnson
2003-08-19 15:14 ` Richard B. Johnson
2003-08-19 15:30 ` Jeff Garzik
2003-08-19 16:52   ` David Mosberger
2003-08-19 17:22   ` Matti Aarnio
2003-08-19 18:00   ` J.A. Magallon
2003-08-19 20:02     ` Richard B. Johnson
2003-08-22  2:31       ` Sulaiman Alhasawi
2003-08-22  7:25         ` Paul Rolland
2003-08-22  8:33         ` Geert Uytterhoeven
2003-08-22 10:35           ` Måns Rullgård
2003-08-23 13:16             ` Leandro Guimarães Faria Corsetti Dutra
2003-08-19 19:18 ` Vojtech Pavlik
2003-08-19 23:34 ` Andrei Barbu "T'Eval"
2003-08-22  9:36 P. Christeas
2003-08-22  9:51 ` Christoph Hellwig
2003-08-22 13:58   ` Kurt Wall
2003-08-22 12:37 ` Con Kolivas

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=3F4437E7.2090307@longlandclan.hopto.org \
    --to=stuartl@longlandclan.hopto.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=davidsen@tmr.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

all inboxes | Powered by JetHome®