Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] The Great Renaming (of netperf-wrapper): Final contenders
Date: Tue, 14 Apr 2015 10:42:34 -0400	[thread overview]
Message-ID: <3BF5C1C0-A2D2-4F62-829C-16E54EE6F945@gmail.com> (raw)
In-Reply-To: <87pp782wbt.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

I like names based on bashing or smashing.

Not so sure about "flent" - see http://www.amazon.com/Flents-Stopples-Cotton-Plugs-Packaging/dp/B003U76CEI

Rich
On Apr 13, 2015, at 5:48 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Hi everyone
> 
> The Great Renaming (of netperf-wrapper) has now entered its final phase
> (i.e., I have to make a decision now). There's a couple of contenders
> for a new name, see below. I'd like some feedback on which you prefer. A
> simple "This one!" is fine, but reasoning about why is also appreciated,
> of course :)
> 
> So, without further ado, the contenders are:
> 
> - "ENT: The Extensible Network Tester".
>  Possible name clash: https://packages.debian.org/sid/ent
> 
> - "Exnett: The EXtensible NETwork Tester"
>   Avoids the name clash; the second t is important for this.
> 
> - "Flent: The Flexible Network Tester"
>  'Flent' is also the sound a bufferbloated network makes when subjected
>  to testing :)
> 
> - "NetBasher"
> 
> For the first three, the abbreviation would probably be the everyday
> name, name of the executable, etc, with the expansion added in
> descriptions where appropriate.
> 
> 
> Please comment by Thursday, as I have a deadline for something that
> needs to include the name then...
> 
> Thanks in advance! :)
> 
> -Toke
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

       reply	other threads:[~2015-04-14 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87pp782wbt.fsf@toke.dk>
2015-04-14 14:42 ` Rich Brown [this message]
2015-04-14 15:51   ` Richard Smith

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BF5C1C0-A2D2-4F62-829C-16E54EE6F945@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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