9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] prefered naming conventions (Tvx-*, tvx*, etc.)
Date: Sat, 29 May 2010 06:51:44 -0400	[thread overview]
Message-ID: <8cd0c224a8694b6e20d34747b0975810@kw.quanstro.net> (raw)
In-Reply-To: <2ed55bf4bfd3d73f733d9b27186255a6@swcp.com>

> I see renaming Tvx to tvx, and Tvx-root to tvxroot.  What is the
> preference with the docs and the source.  tvxrootsrc seems a bit unwieldy,
> and I've always liked using '-' or '_' to separate out words for
> readability, but this seems to NOT be Plan 9's communities preference.

perhaps you could drop "root"?  perhaps "tvx" and "tvxsrc"?
if root must stay, i'd still omit the separator.

- erik



  reply	other threads:[~2010-05-29 10:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29  5:55 EBo
2010-05-29 10:51 ` erik quanstrom [this message]
2010-05-29 11:19   ` EBo
2010-05-29 17:28 ` ron minnich
2010-05-29 18:42   ` EBo

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=8cd0c224a8694b6e20d34747b0975810@kw.quanstro.net \
    --to=quanstro@quanstro.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).