From: patv@monmouth.com (Pat Villani)
Subject: [TUHS] 32I status as of 17 Nov 2003
Date: Mon, 17 Nov 2003 22:40:51 -0500 [thread overview]
Message-ID: <3FB994C3.2020404@monmouth.com> (raw)
In-Reply-To: <20031117.162016.84000120.imp@bsdimp.com>
M. Warner Losh wrote:
> I'm not a lawyer, but I've had to deal with IP lawyers while being on
> FreeBSD core team and other places enough to know a problem area when
> I see it.
Absolutely correct, Warner. Even calling it UNX, after the DEC site
code, is asking for trouble. Needless to say, it won't be called unix,
or anything similar, any time soon, if ever.
Pat
--
Most turkeys taste better the day after; my mother's tasted better the
day before. -- Rita Rudner
next prev parent reply other threads:[~2003-11-18 3:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 16:40 patv
2003-11-17 21:41 ` Brantley Coile
2003-11-17 22:17 ` M. Warner Losh
2003-11-17 22:48 ` Brantley Coile
2003-11-17 23:20 ` M. Warner Losh
2003-11-18 3:40 ` Pat Villani [this message]
2003-11-18 3:19 ` Pat Villani
2003-11-18 0:13 macbiesz
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=3FB994C3.2020404@monmouth.com \
--to=patv@monmouth.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).