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
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 16 Oct 2000 17:46:22 -0400
To: cygwin AT sources DOT redhat DOT com
Subject: Re: A standard bug-reporting program for cygwin
Message-ID: <20001016174622.A15426@cygnus.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: cygwin AT sources DOT redhat DOT com
References: <20001016160136 DOT A12621 AT cygnus DOT com> <39EB752C DOT 76F49822 AT home DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <39EB752C.76F49822@home.com>; from superbiskit@home.com on Mon, Oct 16, 2000 at 05:37:48PM -0400

On Mon, Oct 16, 2000 at 05:37:48PM -0400, David A. Cobb wrote:
>Is there a good technical reason why an existing open-source system,
>such as Bugzilla, is inappropriate?

Probably because if something like that was set up, only Earnie Boyd and
I would subscribe to it and we'd get even more cranky answering all of
the questions than we already are. :-)

IMO, 99% of the "bugs" that are reported here are really cockpit errors.
I tremble at the thought of actually setting up something like GNATS or
BugZilla for this project.  We'd be swamped with "syntax error before
'foo'" and "I can't build a DLL" "bugs".

This is speculation, of course, but I do have the experience of seeing
exactly this on the Cygwin to-do list.  People try to use this as a bug
reporting utility or to ask for improvements to apache.  I suspect that
setting up a "bug tracking" system for cygwin would be very similar.

That's why I'd like the "bugs" to come here, where the collective
knowledge can be used to answer questions without going through the due
diligence of a bug tracking system.

Who knows, though.  If this works out maybe we could set up a cygwin bug
tracking system, too.

cgf

>Chris Faylor wrote:
>> I'd like to set up a shell script or program which could be run to generate
>> text to be sent to the cygwin mailing list.
>>
>> It would ask a limited number of questions and generate a text file appropriate
>> for mailing here.
>>
>>   My idea would be for the script to run 'cygcheck -r -s -v' and then ask
>>
>>   What program is causing problems (e.g., gcc, bash, awk, etc)?
>>
>>   Describe the problem in detail (a simple test case would be appreciated):
>>
>>   Enter the name of any associated files needed to generate the problem.
>>   .
>>   .
>>   .
>>   Created file xxx.  Please send this file to cygwin AT sources DOT redhat DOT com with the
>>   subject "bug report".
>>
>> Does this make sense?  My goal is to cut down on the back and forth of the "I can
>> provide details if necessary".  "Yes.  Provide details."

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