Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Sat, 29 Mar 2003 17:20:31 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Mozilla 1.3 built on cygwin?
Message-ID:	<20030329222031.GA23834@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20030329001348 DOT GA1533 AT redhat DOT com> <002701c2f632$71814490$fc5f07d5 AT BRAMSCHE>
Mime-Version:	1.0
In-Reply-To:	<002701c2f632$71814490$fc5f07d5@BRAMSCHE>
User-Agent:	Mutt/1.5.1i

On Sat, Mar 29, 2003 at 09:33:23PM +0100, Ralf Habacker wrote:
>>I don't have the code anymore
>
>It's a pity, because everbody else has to start from scratch and
>couldn't take a deeper look and perhaps find the problem.

And the reason you wanted thousands of people to know this is...?

If you have such great insight into this type of thing, it won't take
you any time at all to duplicate.  You've been complaining about this
and other cygwin performance issues for months.  Why don't *you* do
something?  I figured fork/exec/signals out from scratch.  Certainly the
brighter bulbs than I who would be finding the problem would have no
problems generating a new and better implementation.  It's a wonder why
no one has done so yet.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -