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
Date: Tue, 22 Jun 2004 17:23:47 +0800
From: "Xuefer" <Xuefer AT 21cn DOT com>
Reply-To: Xuefer AT 21cn DOT com
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: Re: i wonder when will cygwin use copy on write fork)(
Organization: oursky
Mime-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: Xuefer
X-AIMC-MAILFROM: Xuefer AT 21cn DOT com
Message-ID: <6r959377827483.22974@send5.inner-21cn.com>
X-IsSubscribed: yes

Corinna Vinschen:

	i searched, but can't find. so many unrelative topics
which keyword do u recommend?

======= Original Message 2004-06-22 17:01:30: =======

>On Jun 22 16:46, Xuefer wrote:
>> the current implement non-copy on write is damn slow.
>> especially configure scripts, which has soo many forks
>
>Read the mailing list archives.
>
>Corinna
>
>-- 
>Corinna Vinschen                  Please, send mails regarding Cygwin to
>Cygwin Co-Project Leader          mailto:cygwin AT cygwin DOT com
>Red Hat, Inc.
>
>--
>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/
>

= = = = = = = = = = = = = = = = = = = =



--
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/