From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] 9base fork renamed to frontbase
Date: Fri, 9 Sep 2016 23:41:53 -0400 [thread overview]
Message-ID: <efcfd99cc8278a29d16b7ad319233234@dl.attlocal.net> (raw)
In-Reply-To: <20160910032722.GB17158@wopr>
>> Proposed new changes:
>>
>> - Use $9FRONT instead of $PLAN9 to avoid stepping on 9base or
>> plan9port.
>
> $9FRONT is not a valid identifier in sh(1). I propose we use $GOROOT
> instead.
How about $PLAN9FRONT?
sl
next prev parent reply other threads:[~2016-09-10 3:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 2:22 sl
2016-09-10 3:27 ` [9front] " Kurt H Maier
2016-09-10 3:41 ` sl [this message]
2016-09-10 4:28 ` Kurt H Maier
2016-09-10 6:42 ` Ian Sutton
2016-09-11 1:43 ` sl
2016-09-11 6:40 ` Kurt H Maier
2016-09-11 9:52 ` Ian Sutton
2016-09-11 9:58 ` Ian Sutton
2016-09-11 23:39 ` kokamoto
2016-09-12 0:10 ` kokamoto
2016-09-11 1:45 ` sl
2016-09-11 5:51 ` kokamoto
2016-09-11 6:05 ` stanley lieber
2016-09-11 14:39 ` Dave MacFarlane
2016-09-10 12:14 ` kokamoto
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=efcfd99cc8278a29d16b7ad319233234@dl.attlocal.net \
--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).