From: rob@research.att.com
To: sam-fans@hawkwind.utcs.toronto.edu
Date: Mon, 15 Feb 1993 21:06:45 -0500 [thread overview]
Message-ID: <93Feb15.211027est.2763@hawkwind.utcs.toronto.edu> (raw)
i used the wrong word; i should have said 'versions'.
in the last round, i added the exchange of version
number between host and terminal, so changes can
be made compatibly. the issue is letting old
sams and samterms operate with new samterms
and sam.
in this case, at the point the addresses are
exchanged, the version number could be checked and
either 64-bit addresses used (the most general
answer) or an offset.
-rob
reply other threads:[~1993-02-16 2:10 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.211027est.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).