X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Mon, 26 May 2008 09:17:22 -0400 From: "Mark J. Reed" To: cygwin AT cygwin DOT com Subject: Re: Current Cygwin version? Cc: cygwin AT garydjones DOT name In-Reply-To: <483AB774.9040306@byu.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <388a57b20805260549l1927fd41t6b141316630d9c91 AT mail DOT gmail DOT com> <483AB774 DOT 9040306 AT byu DOT net> X-Google-Sender-Auth: 7ce8eb5786f58e6c X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Yeah, we get it, it's a known bug, if you upgrade to 1.7, things break. That doesn't answer the question. Was the release of 1.7 an intentional release of an unfortunately broken release, or the accidental promotion of still-in-development code? -- 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/