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, 14 Jun 2003 20:04:36 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Patch to allow CVS cygwin enable-malloc-debugging to compile
Message-ID: <20030615000436.GC11629@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <OF2D73DA40 DOT 84280E1B-ON86256D44 DOT 006915E0 AT ingerrand DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF2D73DA40.84280E1B-ON86256D44.006915E0@ingerrand.com>
User-Agent: Mutt/1.4.1i

On Fri, Jun 13, 2003 at 02:20:47PM -0500, Michael Checky wrote:
>On Thu, 12 Jun 2003, Christopher Faylor wrote:
>> Don't bother.  This patch is unacceptable for cygwin.  Randomly adding
>> '#if 0' to a header and '#ifndef __CYGWIN__' to cygwin code is not ever
>> going to be accepted.
>
>I didn't submit the patch to be applied to the cygwin sources,

Um, yeah.  I told you not to bother doing so, in fact.  Then I told you
why you shouldn't bother.  Seems pretty clear.  I guess we are all in
agreement.

cgf

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