From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com, mrjoel@lixil.net
Subject: Re: [Adopt] Iperf package [2.0.13].
Date: Sat, 09 Feb 2019 20:12:00 -0000 [thread overview]
Message-ID: <85f100c2-b952-7e64-e085-8ea4efe87318@gmail.com> (raw)
In-Reply-To: <1549546211360-0.post@n5.nabble.com>
Am 07.02.2019 um 14:30 schrieb Battu kaushik:
> >>so I am wondering if these two requests are related or not.
> Yes, two requests are same. You can prefer my request (As, i have already
> discussed with Bob).
>>> I don't see you listed as a project member
> Now, it has been added.
>
> I have tested on both archs
> x86:https://drive.google.com/drive/folders/1IGKvAqB2Dbditb43RYjZ4js6XSdAmmwb
> x86_64:
> https://drive.google.com/drive/folders/1tyvaczV29n5kT3cH_myXTaCoOP6LiRP4
>
> iperf2013.cygport
> <http://cygwin.1069669.n5.nabble.com/file/t11471/iperf2013.cygport>
>
> Thanks,
> Kaushik.
>
the binary packages have no access permission.
The cygport looks fine, it builds with no issue.
But, IMHO, it should be called just iperf.cygport
Tocal test on 64 bit version works.
From my point of view, you can adopt it, as
Joel Johnson has not answered to the request of feedback.
Please see for next step
https://cygwin.com/package-upload.html
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-09 20:12 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 [this message]
2019-02-13 6:40 ` Battu kaushik
2019-02-20 3:30 ` Joel Johnson
2019-02-20 7:35 ` Kaushik Battu
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=85f100c2-b952-7e64-e085-8ea4efe87318@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=mrjoel@lixil.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).