From: rob@research.att.com
To: sam-fans@hawkwind.utcs.toronto.edu
Date: Mon, 15 Feb 1993 22:44:32 -0500 [thread overview]
Message-ID: <93Feb15.224728est.2763@hawkwind.utcs.toronto.edu> (raw)
you're missing nothing except the possibility of incompatibility
with existing binaries of sam and samterm, which is probably
a minor issue for most sam users, who are in the small minority
in their local shops. oh, and the fact that '32 bit address' is
a fine token when you're implementing sam on a vax 750 in 1985.
-rob
reply other threads:[~1993-02-16 3:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=93Feb15.224728est.2763@hawkwind.utcs.toronto.edu \
--to=rob@research.att.com \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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).