Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Wed, 6 Dec 2000 14:31:53 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: CONFIRM subscribe to cygwin-apps AT cygwin DOT com Message-ID: <20001206143153.I8257@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20001204135109 DOT A26389 AT redhat DOT com> <20001204141650 DOT A26708 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from fujieda@jaist.ac.jp on Tue, Dec 05, 2000 at 08:39:48PM +0900 On Tue, Dec 05, 2000 at 08:39:48PM +0900, Kazuhiro Fujieda wrote: >>>> On Mon, 4 Dec 2000 14:16:50 -0500 >>>> Christopher Faylor said: > >> > Is there a bug tracking system? >> >> No. I've toyed with implementing one but I just don't have the will >> to wade through the "Is cygwin work on Bushwa gcc?" messages that will >> inevitably result from doing this. > >I agree with you. I, however, believe a bug tracking system >itself is meaningful. Users may be able to find a bug to be >fixed in the system before they complain to the cygwin ML of it. >If you limit writable access to a few members, you can keep away >from meaningless messages. I don't think that there is much chance of people who read the cygwin mailing list figuring out what the error means or how it applies to them. However, I can see why a bug tracking list might be useful to people with a clue. I'll look into setting something up but it won't be soon. Setting up GNATS is an incredibly tedious and error-prone process. I keep waiting for "somebody" to automate the process on sources.redhat.com. cgf