From: Elliott.Hughes@genedata.com Elliott.Hughes@genedata.com
Subject: [9fans] allowing long file names with a space too
Date: Tue, 14 Apr 1998 11:56:08 +0200 [thread overview]
Message-ID: <19980414095608.oNl7jv9h-ySv8151Fagm1wdJyQfU3Obe_F9Fm9tlH8o@z> (raw)
> The idea is to only send the variable data in 9P, so the
> "machine independent encoding" stays fixed length. The mount
> driver will do the "right thing".
So why bother with an upper limit on length at all? Why trade one
hard-coded assumption for another? Because you're implementing
some specific protocol?
--
http://users.ch.genedata.com/~enh/
next reply other threads:[~1998-04-14 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-14 9:56 Elliott.Hughes [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-04-14 15:05 G.David
1998-04-14 9:52 Elliott.Hughes
1998-04-10 23:16 G.David
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=19980414095608.oNl7jv9h-ySv8151Fagm1wdJyQfU3Obe_F9Fm9tlH8o@z \
--to=elliott.hughes@genedata.com \
/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).