9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Fariborz 'Skip' Tavakkolian" <fst@real.com>
To: 9fans@cse.psu.edu
Subject: [9fans] 9P to 9P2000 migration path
Date: Sun, 28 Jan 2001 10:44:27 -0800	[thread overview]
Message-ID: <3.0.5.32.20010128104427.014da910@mail.real.com> (raw)
In-Reply-To: <20010127215828.D7A06199D5@mail.cse.psu.edu>

This is great news; Thanks for including us early
on this. There is always a risk of getting bogus
feedback because the nuances may be missed.
The next question may be one of those :-)

What is the migration strategy for 9P to 9P2000? Is
there consideration given to operating a network in
mixed mode (9P/9P2000) and what it would take to
do so? Is there a provision for protocol versioning?

Thanks.



  parent reply	other threads:[~2001-01-28 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-27 21:58 [9fans] 9P2000 rob pike
2001-01-28 16:29 ` Sam Ducksworth
2001-01-28 18:44 ` Fariborz 'Skip' Tavakkolian [this message]
2001-01-30  9:21 ` Mike Haertel
2001-01-28 19:23 [9fans] 9P to 9P2000 migration path rob pike
2001-01-29  5:19 ` Dan Cross
2001-02-02  1:31 jmk
2001-02-05 18:29 ` Dan Cross

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=3.0.5.32.20010128104427.014da910@mail.real.com \
    --to=fst@real.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).