From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: re: [9fans] blanks in names
Date: Thu, 4 Jul 2002 15:41:42 -0400 [thread overview]
Message-ID: <877850.1025797302@GOLD> (raw)
It always will. The only reason spaces arrive in file names is
that they are imported from outside.
-rob
--On Thursday, July 04, 2002 7:47 AM +0100 forsyth@caldo.demon.co.uk wrote:
>>> otherwise, Plan 9 should prohibit space in its file names, as
>>> previously, ...
>
> i ought to have said `and still', since /sys/src/fs/port/9p2.c still
> blocks it. perhaps just as well until it's sorted out!
>
next reply other threads:[~2002-07-04 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 19:41 rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-04 16:47 rog
2002-07-04 17:06 ` FJ Ballesteros
2002-07-04 22:29 ` arisawa
2002-07-04 6:47 forsyth
2002-07-04 19:45 ` rob pike, esq.
2002-07-04 14:56 ` FJ Ballesteros
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=877850.1025797302@GOLD \
--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).