X-Spam-Check-By: sourceware.org Message-ID: <44971306.8030109@tlinx.org> Date: Mon, 19 Jun 2006 14:11:34 -0700 From: Linda Walsh User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Latest Cygwin Release 5 month old... References: <002401c690e2$6f2656b0$0a3b6080 AT joehome> <449208C4 DOT 4CF28807 AT dessent DOT net> <4495C806 DOT 2020805 AT tlinx DOT org> <4495D125 DOT 4693156F AT dessent DOT net> In-Reply-To: <4495D125.4693156F@dessent.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Brian Dessent wrote: > > The last release of Cygwin was 1.5.19-4 on 2006-01-20, so unless you > have a time machine, a fix made on 2006-05-17 will not be included. > Besides, using the latest snapshot should always be the first thing you > try when encountering a problem before reporting it to the list. Nobody > cares about hearing about bugs that have already been fixed. > -=-=-=- Nobody like to hear "oh, it's fixed in the latest build, but not in the released product." If a developer doesn't think it is good enough to release, then I'm not sure I want to be testing on my "production" machine. Not everyone has a spare test machine. -l -- 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/