From: boyd.roberts@ca-indosuez.com
To: 9fans@cse.psu.edu
Subject: [9fans] Réf. : [9fans] october 14 package patch
Date: Wed, 29 Nov 2000 12:17:15 +0100 [thread overview]
Message-ID: <412569A6.003E697F.00@SNPAR12.> (raw)
/29000/include/u.h 2f0000004503000000000000868b0100
/29000/include/ureg.h 2f0000001903000000000000868b0100
/29000/mkfile 2f0000002e000000000000003e8b0100
/386/9load 2f000000e0370200000000003c8b0100
...
that's scarey. look at the high bits and the low bits the of checksums.
next reply other threads:[~2000-11-29 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 11:17 boyd.roberts [this message]
2000-11-29 13:27 boyd.roberts
2000-11-29 18:58 Russ Cox
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=412569A6.003E697F.00@SNPAR12. \
--to=boyd.roberts@ca-indosuez.com \
--cc=9fans@cse.psu.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).