From: matt@aclaro.com (Matthew Mastracci)
Subject: [TUHS] Fwd: Helping in the battle against SCO
Date: Wed, 10 Sep 2003 14:18:15 -0600 [thread overview]
Message-ID: <3F5F8707.7070504@aclaro.com> (raw)
What about comparing SVR1/2 to 2.4.x? SCO seems to be picking on the
early 2.4.x codebase. This should also pick up the SGI code comments in
the malloc() function that were recently publicized, though I'm not sure
which version Linus removed the code from.
Matt.
next reply other threads:[~2003-09-10 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 20:18 Matthew Mastracci [this message]
2003-09-10 23:17 ` Warren Toomey
-- strict thread matches above, loose matches on Subject: below --
2003-09-15 20:39 Norman Wilson
2003-09-16 3:01 ` M. Warner Losh
2003-09-10 23:59 Norman Wilson
2003-09-11 0:41 ` Andru Luvisi
2003-09-11 17:32 ` Greg Lehey
2003-09-11 17:25 ` Greg Lehey
2003-09-09 22:02 Warren Toomey
2003-09-10 1:14 ` Maciek Bieszczad
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=3F5F8707.7070504@aclaro.com \
--to=matt@aclaro.com \
/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;
as well as URLs for NNTP newsgroup(s).