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
Message-ID: <028e01c1594f$47cf7030$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Grant Edwards" <grante AT visi DOT com>, <bgat AT billgatliff DOT com>
Cc: <cygwin AT cygwin DOT com>, <gdb AT sources DOT redhat DOT com>
References: <20011018161003 DOT A3059 AT saturn DOT billgatliff DOT com> <20011018222406 DOT C11830 AT redhat DOT com> <20011019085618 DOT A5013 AT saturn DOT billgatliff DOT com> <20011019114712 DOT A23101 AT visi DOT com>
Subject: Re: [1.3.3] breaks serial i/o?
Date: Sat, 20 Oct 2001 20:09:17 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 20 Oct 2001 10:14:09.0073 (UTC) FILETIME=[F4FF1210:01C1594F]

Somebody who thinks problems are fixed without details wrote:
>
> Somebody in a bad mood wrote:
>
> > >Suggestions, patches, signs of moral support, etc. would all be
most
> > >graciously accepted.  Thanks for the help,
> >
> > No suggestions, patches, or signs of moral support here.
>
> The why not just shut-the-hell-up?

That would *really* help someone who indicated they had a tight timeline
to solve their problem in. Getting an authoritative answer is the best
they could hope for - and they got it.

> Do you post snotty replies to every question for which you
> don't know the answer?  Shit, man, are you trying to
> single-handedly give open-source a bad name?

You didn't read Chris' email carefully did you. He knows the answer. He
gave it. For clarity the answer was (paraquoted)

1. No known fault here.
2. We cannot reproduce the fault (because the report gave almost NO
details).
3. If the fault is to be fixed pre 1.3.4 (which the report indicated was
a goal) then details are needed to reproduce it.

And not stated, but pretty obvious from a look at the website, and
previous activity on bugs - We *would* like to fix this so *please* go
and generate enough details so we can do that.

> I've met Bill, and I'm pretty sure he was aware of what he
> typed.
>
> He's reporting a problem he's having with gdb on a particular
> platform and asking if anybody knows anything about it.
>
> There's nothing wrong with that.

There's a lot wrong if you *expect* anything to *happen* as a result of
writing the report.

That's like saying "I have a problem with pthreads on linux kernel foo,
help." and expecting a useful reply. Ha!

You might like to read Eric S Raymonds essay on getting help from open
source groups.

Rob


--
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/