From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] comments on renaming iperf 2 to iperf next generation
Date: Tue, 16 Aug 2022 14:10:50 -0700 [thread overview]
Message-ID: <CAHb6LvrzE37ZS+pQor8tLPQE+sj8CcirHcznpBCzxwVGHwwMjw@mail.gmail.com> (raw)
In-Reply-To: <EF36A9ED-AD30-445D-B562-4291F6521DD6@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2095 bytes --]
Yeah, I got some input to just leave things as is so you're not alone in
your "random neurons firing."
My goal is to minimize confusion. Changing the binary name from iperf to
something else is something I'd like to avoid.
Changing the name and description in sourceforge may only cause more
confusion. Hence the pseudo polling here to see what others think.
Bob
On Tue, Aug 16, 2022 at 1:54 PM Rich Brown via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:
>
> I don't necessarily like or endorse any of these... Just some random
> neurons firing.
>
> - If you're going to change the (full) name, would you also change the
> name on the command line?
> - If you did, it might be to something like "iperfnext", which is long
> - Or perhaps "iperfx" but that's hard to type that final X (my ring finger
> doesn't get down there as easily)
> - "iperfx" is an anagram for "prefix"
> - What about "iperfect"? :-)
> - "xperf" is easier to type, is short. And there's a program called
> "Xperf" Dang.
> - Maybe there's a way to work "responsiveness" and "performance" into the
> name "res-perf"? "resperf"
>
> I dunno.
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #1.2: Type: text/html, Size: 2853 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
next prev parent reply other threads:[~2022-08-16 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.590.1660681819.1281.make-wifi-fast@lists.bufferbloat.net>
2022-08-16 20:54 ` Rich Brown
2022-08-16 21:10 ` Bob McMahon [this message]
2022-08-16 18:54 Bob McMahon
2022-08-16 20:04 ` Sebastian Moeller
2022-08-16 20:30 ` Bob McMahon
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHb6LvrzE37ZS+pQor8tLPQE+sj8CcirHcznpBCzxwVGHwwMjw@mail.gmail.com \
--to=bob.mcmahon@broadcom.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
/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