From: Kaushik Battu <battuk25@gmail.com>
To: cygwin-apps@cygwin.com
Cc: Marco Atzeri <marco.atzeri@gmail.com>
Subject: Re: [Adopt] Iperf package [2.0.13].
Date: Wed, 20 Feb 2019 07:35:00 -0000 [thread overview]
Message-ID: <CANg-PA-42kY5=Xkp=KC=c2MfigfdtN1vXAnyomLXL_b4HuzQvA@mail.gmail.com> (raw)
In-Reply-To: <ed3df62fbdca6b8b751fc4b31cf4ce56@lixil.net>
Thanks Joel.
I have tried to upload 2.0.13 package.
$ cygport iperf.cygport up
>>> Uploading iperf-2.0.13-1.i686
>>> Running lftp sftp://cygwin@cygwin.com
Password:
cd ok, cwd=/x86/release
Transferring file `iperf-2.0.13-1-src.tar.xz'
Transferring file `iperf-2.0.13-1.hint'
Transferring file `iperf-2.0.13-1.tar.xz'
Making directory `iperf-debuginfo'
Transferring file `iperf-debuginfo/iperf-debuginfo-2.0.13-1.hint'
Transferring file `iperf-debuginfo/iperf-debuginfo-2.0.13-1.tar.xz'
Total: 1 directory, 5 files, 0 symlinks
New: 5 files, 0 symlinks
605745 bytes transferred in 5 seconds (110.3 KiB/s)
Upload complete.
Iperf3 is limited in features (as it is single threaded). For testing
throughput/Latency on wlan interfaces still people prefer to use iperf2.
- Battu.
On Wed, 20 Feb 2019 at 09:01, Joel Johnson <mrjoel@lixil.net> wrote:
> I've been away from email access the past bit and am just getting back.
> I originally refrained from updating the package to the iperf2 fork
> since at the time it wasn't clearly endorsed. Now that the original
> project recommends it as an alternative to iperf3 I don't have any
> objection to it being updated.
>
> Joel
>
> On 2019-02-01 09:05, Marco Atzeri wrote:
> > Am 29.01.2019 um 04:13 schrieb Kaushik Battu:
> >> Iperf package has not been updated from long time ago, it looks to be
> >> in
> >> orphaned stage. I would like to maintain the iperf package and upgrade
> >> it
> >> to version-2.0.13 .
> >>
> >> Here are the enhancements of iperf 2.0.13 :
> >> https://sourceforge.net/projects/iperf2/
> >>
> >> Regards,
> >> Kaushik Battu.
> >>
> >
> > Kaushik,
> > for an ITA (Intention to Adpot) you should
> > provide a working copy for both arch of
> > the packages for evaluation.
> >
> > This of course assuming that Joel Johnson is not anymore
> > interested to be the maintainer.
> > Joel please let us know
> >
> > Regards
> > Marco
> >
> >
> >
> > ---
> > Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> > https://www.avast.com/antivirus
>
next prev parent reply other threads:[~2019-02-20 7:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 3:13 Kaushik Battu
2019-02-01 16:05 ` Marco Atzeri
2019-02-07 13:32 ` Battu kaushik
2019-02-09 20:12 ` Marco Atzeri
2019-02-13 6:40 ` Battu kaushik
2019-02-20 3:30 ` Joel Johnson
2019-02-20 7:35 ` Kaushik Battu [this message]
2019-02-20 20:16 ` Achim Gratz
2019-02-20 20:36 ` Achim Gratz
2019-03-14 20:20 ` Achim Gratz
2019-05-01 18:20 ` Kaushik Battu
2019-05-01 19:15 ` Achim Gratz
2019-05-01 19:29 ` Brian Inglis
2019-05-02 18:01 ` Jon Turney
2019-02-02 9:20 ` Achim Gratz
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='CANg-PA-42kY5=Xkp=KC=c2MfigfdtN1vXAnyomLXL_b4HuzQvA@mail.gmail.com' \
--to=battuk25@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=marco.atzeri@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).