From: stanley lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] inquery: plans for phasing out cpu, rx and import
Date: Mon, 08 Aug 2016 11:22:22 -0400 [thread overview]
Message-ID: <4e9d0704-05fc-4ca6-bd17-6a28ea6b9834@email.android.com> (raw)
In-Reply-To: <6dbdcfebbdb64790613a1f1501d5076e@titan.jitaku.localdomain>
kokamoto@hera.eonet.ne.jp wrote:
>> Old cpu is the *only* way to connect to Plan 9 from Bell Labs.
>>
>> 9front will have old cpu listeners disabled by default.
>
>I think I understand your words.
>I just pointed the rational result, if we push rcpu.
>
>Kenji
I don't think I understand the danger. 9front users will not be able to devolve to old cpu out of habit when connecting to 9front because on 9front old cpu listeners will be disabled by default. When connecting to Plan 9 from Bell Labs old cpu is the only option, so renaming the old cpu commands will only haven the effect of causing Plan 9 users to have to mentally replace all documented commands with the new names. 9front's new cpu commands already have new names, and existing documentation refers to them by those names.
Renaming the old cpu commands will only cause confusion.
sl
next prev parent reply other threads:[~2016-08-08 15:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 19:39 cinap_lenrek
2016-08-07 2:25 ` [9front] " sl
2016-08-07 23:55 ` kokamoto
2016-08-08 1:37 ` sl
2016-08-08 7:38 ` kokamoto
2016-08-08 15:22 ` stanley lieber [this message]
2016-08-08 15:53 ` hiro
2016-08-08 16:33 ` cinap_lenrek
2016-08-09 9:45 ` hiro
2016-08-09 14:57 ` Kurt H Maier
2016-08-09 15:12 ` stanley lieber
2016-08-09 17:46 ` cinap_lenrek
2016-08-09 15:09 ` stanley lieber
2016-08-09 15:33 ` Kurt H Maier
2016-08-11 8:47 ` Steve Simon
2016-08-09 17:44 ` cinap_lenrek
2016-08-09 17:56 ` stanley lieber
2016-08-09 17:49 ` cinap_lenrek
2016-08-09 17:59 ` stanley lieber
2016-08-10 10:04 ` hiro
2016-08-08 15:54 ` cinap_lenrek
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=4e9d0704-05fc-4ca6-bd17-6a28ea6b9834@email.android.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/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).