From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plumb
Date: Sat, 1 Dec 2001 22:33:53 -0500 [thread overview]
Message-ID: <20011202033358.A159719A18@mail.cse.psu.edu> (raw)
You're right. There's still plenty of interesting research to do
in the design of name spaces. We have a long list of issues that
we'd like to address, this being one of them.
-rob
next reply other threads:[~2001-12-02 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 3:33 rob pike [this message]
[not found] <rob@plan9.bell-labs.com>
2001-12-02 3:10 ` rob pike
2001-12-02 3:31 ` Scott Schwartz
-- strict thread matches above, loose matches on Subject: below --
2001-12-01 23:57 Boyd Roberts
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=20011202033358.A159719A18@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).