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 To: edward , cygwin-developers AT cygwin DOT com Subject: Re: CONFIRM subscribe to cygwin-apps AT cygwin DOT com References: <20001204135109 DOT A26389 AT redhat DOT com> <20001204141650 DOT A26708 AT redhat DOT com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 05 Dec 2000 20:39:48 +0900 In-Reply-To: Christopher Faylor's message of Mon, 4 Dec 2000 14:16:50 -0500 Message-ID: Lines: 18 X-Mailer: Gnus v5.3/Emacs 19.34 >>> 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. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology