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:	Sun, 5 Oct 2003 13:04:39 -0400
From:	Christopher Faylor <cgf-rcm AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] notice of package removal: gcc2-2.95-*
Message-ID:	<20031005170439.GB10102@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20031005051332 DOT 4028232A8A7 AT redhat DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20031005125150 DOT 0286aeb8 AT 127 DOT 0 DOT 0 DOT 1>
Mime-Version:	1.0
In-Reply-To:	<5.1.0.14.0.20031005125150.0286aeb8@127.0.0.1>
User-Agent:	Mutt/1.4.1i

On Sun, Oct 05, 2003 at 12:52:44PM -0400, Larry Hall wrote:
>At 01:13 AM 10/5/2003, Christopher Faylor you wrote:
><snip>
>
>>Oh, and I probably have to say that the gcc 3.3.1 package will still be
>>available.
>
>Yes but will it work with B20??? ;-)

I don't think it's even an issue.  B20 compiles files for you
automatically and corrects errors on the fly.  So, even if things didn't
work initially, B20, would eventually figure out what was wrong and
correct the problem.

cB20f

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