Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Message-ID: <42A68EBC.AEC3134C@dessent.net>
Date: Tue, 07 Jun 2005 23:22:52 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 1.5.17-1: apache and rebaseall
References: <Pine DOT SOL DOT 4 DOT 43 DOT 0506080005130 DOT 20983-100000 AT hubcap DOT clemson DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Joel Denny wrote:

> I've seen the reports.  I was hoping there were some further developments.
> Is there a list somewhere of unresolved issues?  Or is that the mailing
> list's job?

There's no bug reporting or PR system, so the mailing list pretty much
serves all purposes.  I think the idea has been brought up before, but
the general concensus was that having something like bugzilla would just
lead to more work to traige bugs, prod for good testcases, get full
system details from the reporter, etc.  We already do that on the
mailing list and I don't think people don't want to have to do it in two
places.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/