From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] iperf: bump to version 2.0.9
Date: Fri, 5 Aug 2016 14:24:15 +0300 [thread overview]
Message-ID: <20160805112415.GU3620@tarshish> (raw)
In-Reply-To: <20160805122153.6c4a4593@free-electrons.com>
Hi Thomas,
On Fri, Aug 05, 2016 at 12:21:53PM +0200, Thomas Petazzoni wrote:
> On Sun, 31 Jul 2016 11:25:41 +0300, Baruch Siach wrote:
> > > > Where have you found a link to that repo? Only after googling for "iperf2 git"
> > > > I found an indication to its existence in https://github.com/daynix/iperf2.
> > >
> > > From https://sourceforge.net/projects/iperf2/, click on "Code".
> >
> > That's the first thing I tried. Looking there again all I see is an old Svn
> > repo (last update is r8 from 2014-09-14). What am I missing?
>
> Then we don't have the same Internet I'm afraid. Here the "Code" tab
> points to https://sourceforge.net/p/iperf2/code/ci/master/tree/ which
> is a Git repository with the latest commit on July 2, 2016.
Now I see it. There are TWO "Code" links at
https://sourceforge.net/projects/iperf2/. The left one (between "Wiki" and
"Tickets") points to the current git repo, while the right one (right most)
points to the old Svn repo. I'm just used to look for the "Code" link at the
right on SF project's summary pages.
Thanks,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-08-05 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 9:26 [Buildroot] [PATCH] iperf: bump to version 2.0.9 Baruch Siach
2016-07-29 18:55 ` Khem Raj
2016-07-30 12:31 ` Thomas Petazzoni
2016-07-31 4:38 ` Baruch Siach
2016-07-31 8:09 ` Thomas Petazzoni
2016-07-31 8:25 ` Baruch Siach
2016-08-05 10:21 ` Thomas Petazzoni
2016-08-05 11:24 ` Baruch Siach [this message]
2016-08-05 12:02 ` Thomas Petazzoni
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=20160805112415.GU3620@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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