From: Marius Bakke <mbakke@fastmail.com>
To: Benz Schenk <benz.schenk@uzh.ch>, guix-devel@gnu.org
Subject: Re: [PATCH] Add iPerf
Date: Tue, 18 Oct 2016 22:37:40 +0100 [thread overview]
Message-ID: <87funt72zf.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161018180646.48bbb60d@gondolin.arda>
Benz Schenk <benz.schenk@uzh.ch> writes:
> Hi
>
> This is my first patch, it's really straight-forward.
> But I'm not quite sure about the naming because there's iperf, iperf2
> and iperf3 which are different projects. The original iperf is
> abandoned and iperf2 is backwards compatible and still gets bug fixes
> and iperf3, which this patch is for, is in active development and adds a
> lot of new features but also lacks some of the options of previous
> versions. Thus it's often referred to as iperf3, which is also the name
> of the binary, so I'm not sure wheter the package should better be
> called iperf3 or iperf.
Hi Benz,
Thanks for this patch! I think naming it "iperf" is fine, even though
the binary and manual is called iperf3. If we need iperf2 later it can
be packaged as "iperf@2".
I'm not sure about the home page: the manual and github page both list
http://software.es.net/iperf/ as the home. What is the relation between
iperf.fr and this project? Should we not go with the official source?
Other than that I'd like to make the following modifications. This can
be done before pushing, no need to send an updated patch:
* Change synopsis to "TCP, UDP and SCTP bandwidth measurement tool".
* Update license to match what's in the LICENSE file.
* Fix minor typos in the description (bandwith->bandwidth).
* Change commit message to match our current convention.
* Download the tarball from http://downloads.es.net/pub/iperf/
Are you okay with these changes (including the home page)?
Thanks again, and welcome! :)
next prev parent reply other threads:[~2016-10-18 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 16:06 [PATCH] Add iPerf Benz Schenk
2016-10-18 21:37 ` Marius Bakke [this message]
2016-10-19 0:07 ` Benz Schenk
2016-10-19 12:23 ` Marius Bakke
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87funt72zf.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=benz.schenk@uzh.ch \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).