public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [Adopt] Iperf package [2.0.13].
Date: Sat, 02 Feb 2019 09:20:00 -0000	[thread overview]
Message-ID: <87zhre8s35.fsf@Rainer.invalid> (raw)
In-Reply-To: <CANg-PA_Fw=+w3dvcBr+LRQtxfeqC+GDoqNZJzypxt6xbwY8Fxw@mail.gmail.com>	(Kaushik Battu's message of "Tue, 29 Jan 2019 08:43:29 +0530")

Kaushik Battu writes:
> 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 .

Did you read

https://cygwin.com/packaging-contributors-guide.html

> Here are the enhancements of iperf 2.0.13 :
> https://sourceforge.net/projects/iperf2/

Over on the main Cygwin list the maintainer for that project essentially
asked the same question as you.  I don't see you listed as a project
member, so I am wondering if these two requests are related or not.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

      parent reply	other threads:[~2019-02-02  9:20 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
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 [this message]

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=87zhre8s35.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.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).