9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] import and p9p
Date: Tue, 20 Jan 2009 19:29:24 -0800	[thread overview]
Message-ID: <dd6fe68a0901201929l75029446kc514c4137076449a@mail.gmail.com> (raw)
In-Reply-To: <df7735866fe35bcd78e07fc02da5088f@quanstro.net>

On Tue, Jan 20, 2009 at 5:47 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> i apologize for the silly question, but
> my p9p-fu is quite weak.
>
> is the reason that plan 9 import is not
> part of p9p other than it was not needed?

it was not needed, and it's not nearly as useful
as the plan 9 one, since the access to 9p
servers is so crippled.

also, you'd need to get tls working.

russ


      parent reply	other threads:[~2009-01-21  3:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  1:47 erik quanstrom
2009-01-21  1:54 ` Roman V. Shaposhnik
2009-01-21  3:29 ` Russ Cox [this message]

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=dd6fe68a0901201929l75029446kc514c4137076449a@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /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).