From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Update
Date: Sun, 12 Nov 2000 09:21:17 -0500 [thread overview]
Message-ID: <20001112142135.4D9E0199DC@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 37 bytes --]
It was incorrect. Weird.
-rob
[-- Attachment #2: Type: message/rfc822, Size: 1475 bytes --]
From: Richard Miller <miller@hamnavoe.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Update
Date: Sun, 12 Nov 2000 09:34:25 0000
Message-ID: <E13utXI-000LOS-0A@finch-post-10.mail.demon.net>
Are you sure the md5sum prefix quoted on the website for the
11 Nov update is correct?
next reply other threads:[~2000-11-12 14:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-12 14:21 rob pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-24 2:15 [9fans] update Skip Tavakkolian
2005-04-25 20:45 jmk
2001-05-26 17:07 [9fans] Update rob pike
2001-04-25 16:15 [9fans] update presotto
2001-03-28 4:59 [9fans] Update rob pike
2000-11-12 9:34 Richard Miller
2000-11-12 13:36 ` Boyd Roberts
2000-11-12 1:33 rob pike
[not found] <rob@plan9.bell-labs.com>
2000-07-29 18:43 ` rob pike
2000-07-29 18:55 ` Scott Schwartz
2000-06-17 18:46 rob pike
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=20001112142135.4D9E0199DC@mail.cse.psu.edu \
--to=rob@plan9.bell-labs.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).