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
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	Andrew DeFaria <ADeFaria AT Salira DOT com>
Subject:	Re: Win2k and cygwin memory leak
Date:	Thu, 07 Aug 2003 15:24:26 -0700
Lines:	12
Message-ID:	<bguji2$l5q$1@main.gmane.org>
References:	<OFAB076707 DOT BB79F906-ON85256D7B DOT 007195C4 AT empirehealthcare DOT com>
Mime-Version:	1.0
X-Complaints-To:	usenet AT main DOT gmane DOT org
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language:	en-us, en, zh
In-Reply-To:	<OFAB076707.BB79F906-ON85256D7B.007195C4@empirehealthcare.com>

Brian DOT Kelly AT empireblue DOT com wrote:

> It would have been "nice" if there was an acknowledgement of this 
> problem (cygwin's or not) rather than attempted character assassinations. 

It has already been acknowledged several times over that it is not a 
problem of Cygwin's rather a problem of Windows. What else do you want? 
When you cluelessly continue to assert that it's a Cygwin memory leak is 
exactly where is leads down the path to character assassinations.

(BTW: Ever think of replacing that Windows box with just a Linux box?)



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

- Raw text -