From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benz Schenk Subject: Re: [PATCH] Add iPerf Date: Wed, 19 Oct 2016 02:07:29 +0200 Message-ID: <20161019020729.6f45c245@gondolin.arda> References: <20161018180646.48bbb60d@gondolin.arda> <87funt72zf.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33286) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bweQ7-0007WL-LO for guix-devel@gnu.org; Tue, 18 Oct 2016 20:07:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bweQ4-0003LE-FW for guix-devel@gnu.org; Tue, 18 Oct 2016 20:07:47 -0400 Received: from idmx02.uzh.ch ([130.60.205.98]:57122) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1bweQ4-0003II-9G for guix-devel@gnu.org; Tue, 18 Oct 2016 20:07:44 -0400 Received: from idsmtp01.uzh.ch ([130.60.206.120]:39681) by idmx02.uzh.ch with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bweQ1-0005cn-Fp for guix-devel@gnu.org; Wed, 19 Oct 2016 02:07:42 +0200 In-Reply-To: <87funt72zf.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Marius Bakke Cc: guix-devel@gnu.org On Tue, 18 Oct 2016 22:37:40 +0100 Marius Bakke wrote: > Benz Schenk 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! :) Sure thing, I just need the software for uni and got this homepage from my advisor. Thank you