Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
Path: not-for-mail
From: "Chris Game" <cgame AT bigfoot DOT com>
Subject: Re: Bugs in Cygnus Tools bash
Date: Tue, 24 Dec 2002 12:37:47 -0000
Lines: 19
Message-ID: <au9knb$lum$2@main.gmane.org>
References: <47D438A0510BD611B9470002A58EDAE7DEC84B AT mchh2a6e DOT mchh DOT siemens DOT de> <03e901c2aa8c$85437850$cd8a9dc0 AT uk DOT aonix DOT com>
X-Complaints-To: usenet AT main DOT gmane DOT org
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1123
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1123

In a recent post, Cliff Hones wrote:

> A word of advice - don't report things as bugs unless you are sure
> they are bugs and not cockpit error - it can make you look
> foolish if you or your configuration are to blame.

That seems a bit harsh. How else are people supposed to figure out
what's wrong if they don't ask? There's no such thing as a stupid
question, and any mis-reported bug gives an opportunity for Cygwin's
usability to be improved - even if it's the documentation! And a few of
us less-than-experts on here benefit from other's mistakes.

-- 
===========================================

Chris Game <chrisgame@!yahoo!dotcodotuk>
===========================================





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/