From: Nick LaForge <nicklaforge@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] naming conventions
Date: Mon, 14 Jun 2010 08:35:24 -0700 [thread overview]
Message-ID: <AANLkTilZ9km4bgC92xS0VvfsbUw993u2zJoIu2CFVkj5@mail.gmail.com> (raw)
In-Reply-To: <51a0fc4b4bb26e2894cc078f681b2bd2@swcp.com>
Would a phonetic morphology à la the ceePlusPlus of wiki would suffice
for our lexically challenged friends?
next prev parent reply other threads:[~2010-06-14 15:35 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
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 [this message]
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=AANLkTilZ9km4bgC92xS0VvfsbUw993u2zJoIu2CFVkj5@mail.gmail.com \
--to=nicklaforge@gmail.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).