9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] naming conventions
Date: Mon, 14 Jun 2010 10:01:30 +0100	[thread overview]
Message-ID: <26f5d4e49bf546e287b3112f0845e47e@terzarima.net> (raw)
In-Reply-To: <2bca08f7e5b22db500c54deb4b58bc0c@swcp.com>

>Is it more reasonable in this case to name the executive vx32 instead of
>9vx since it is a plan 9 emulator for linux?

not really, because vx32 is the library, and 9vx is just one sample application.
(there are others.)



  reply	other threads:[~2010-06-14  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14  8:29 EBo
2010-06-14  9:01 ` Charles Forsyth [this message]
2010-06-14 13:32 ` erik quanstrom
2010-06-14 13:47   ` EBo
2010-06-14 15:16     ` Stanley Lieber
2010-06-14 15:19     ` erik quanstrom
2010-06-14 15:35     ` Nick LaForge
2010-06-14 21:10       ` hiro
2010-06-14 21:24         ` EBo
2010-06-14 21:32           ` erik quanstrom

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=26f5d4e49bf546e287b3112f0845e47e@terzarima.net \
    --to=forsyth@terzarima.net \
    --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).