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 Date: Tue, 28 Dec 2004 18:16:52 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: "Hyperthreading" problems Message-ID: <20041228231652.GC17922@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <41D1D2B2 DOT 4030200 AT exalead DOT com> <41D1DEA4 DOT 1080304 AT exalead DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41D1DEA4.1080304@exalead.com> User-Agent: Mutt/1.4.1i On Tue, Dec 28, 2004 at 11:31:00PM +0100, Stephane Donze wrote: >I am sorry to have to say that, but your message is a very good example >of the fundamental difference between a project that is useable and >reliable, and a project that "almost works" and will never do more that >that. > >[snip] > >If you guys want cygwin to be used by real people, in real life >production or development environments, you should go a bit further than >"I don't have the problem on my computer, so fix it yourself". If you >don't want to or are not able to pay attention to "real world" bugs, >cygwin will probably never be more than an "almost working" program >that runs on your computer the time to take nice screenshots, but fails >miserably when users try to make it work in the real life. You know, if you'd just waited *a week*, you probably could have laid claim to being the first posting of this type in 2005 rather than (hopefully) the last of 2004. I think that being first is usually much more auspicious. So close... -- 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/