Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 10 Oct 2000 10:30:45 -0400
Message-Id: <200010101430.KAA07671@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: Jason DOT Tishler AT dothill DOT com
CC: earnie_boyd AT yahoo DOT com, cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <20001010101156.B1071@dothill.com> (message from Jason Tishler on
	Tue, 10 Oct 2000 10:11:56 -0400)
Subject: Re: download script
References: <20001010131239 DOT 24377 DOT qmail AT web120 DOT yahoomail DOT com> <20001010101156 DOT B1071 AT dothill DOT com>


> From the above, should I conclude that one should not report
> problems unless they are willing to track them down and supply a
> patch?

No, but doing a little work yourself is certainly the fastest way to
get a fix if the fix happens to be trivial.  In the case we're talking
about, the README notes that "direct connect" is missing a lot of
error checking.  Adding error checking is easy but boring.  Adding
error checking is thus something the average developer could help out
with, and also get their bug fixed at the same time if the errors
point out the cause of the problem.

> Obviously, fixing problems and supplying patches is the ideal.

Yup.

> Hopefully, reporting problems with relevant details is still
> considered useful in itself.

Yes, it is.  I keep track of all the setup bugs and I've been trying
to be good about investigating all of them.  But, I'm a busy dude, so
any help from the masses speeds things up.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com