Date: Mon, 4 Feb 2013 11:01:10 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: openssh maintainer?
Message-ID: <20130204160110.GC6230@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <510870CE.7020305@tlinx.org> <20130204122039.GB19792@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130204122039.GB19792@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mon, Feb 04, 2013 at 01:20:39PM +0100, Corinna Vinschen wrote:
>On Jan 29 17:01, Linda Walsh wrote:
>> Who is the person who ports/packages openssh for cygwin?
>
>That's me.
>
>> I was wondering if they could include the HPN patches (High Performance Networking)
>> 
>> http://www.psc.edu/index.php/component/remository/HPN-SSH/OpenSSH-6.0-Patches/
>> 
>> specifically: these two should apply w/no build probs.
>
>Nope.  I won't apply patches which are not included upstream, unless
>they very specificially fix a Cygwin-specific bug.

And, in case it isn't clear, it really is pointless to ask maintainers
to install nonstandard patches into any package unless they adhere to
the above criteria.

Expecting someone to modify a package just for you is rarely going to be
productive.  If you need something nonstandard then build it yourself.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple