From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P2000
Date: Tue, 30 Jan 2001 21:18:53 -0500 [thread overview]
Message-ID: <20010131021857.191FF19A03@mail.cse.psu.edu> (raw)
Consider changing the format of this table to read:
size[4] Tversion[1] tag[2] msize[4] version[s]
Right. This was just a mistake that others have pointed out
and has been fixed.
By the way, one thing I really like about the new encoding is that
emulating the old "fcall" streams module becomes trivial.
There is in fact no fcall any more; the mount driver gets it right.
But this only supports your observation.
-rob
next reply other threads:[~2001-01-31 2:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 2:18 rob pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 9:31 Russ Cox
2001-01-31 17:46 ` Mike Haertel
2001-01-31 2:16 rob pike
2001-01-31 8:56 ` Mike Haertel
2001-01-30 12:09 rog
2001-01-30 18:04 ` Mike Haertel
2001-01-27 21:58 rob pike
2001-01-28 16:29 ` Sam Ducksworth
2001-01-30 9:21 ` Mike Haertel
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=20010131021857.191FF19A03@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).