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, 26 Jul 2003 17:06:26 -0400
From:	Christopher Faylor <cgf-idd AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Apache Bug
Message-ID:	<20030726210626.GD31279@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3F22BA0B DOT 7010008 AT cygwin DOT com> <NDBBLLFMLFMANIDPNADCIEGDFCAA DOT wpmccormick AT covad DOT net>
Mime-Version:	1.0
In-Reply-To:	<NDBBLLFMLFMANIDPNADCIEGDFCAA.wpmccormick@covad.net>
User-Agent:	Mutt/1.4.1i

On Sat, Jul 26, 2003 at 01:45:02PM -0500, Bill McCormick wrote:
>> Can't find it in the archives (I'm sure it's there - I just can't find it)
>> but I think the fix was post 1.3.22.  I'd suggest trying 1.5.  That might
>> be the quickest solution.
>
>Yea that's what I thought. So I tried upgrading to 1.50 last night and must
>have gone a little to far with some of the other Exp packages. I ended up
>with an unusable system

Yeah, the old "unusable system" scenario.  It's a favorite of the 'It failed
to operate for me' bug-reporter crowd.  It's also quite popular with the
"My C program gave me syntax errors.  Can someone help?" set.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sourceware DOT org
and be permanently blocked from mailing lists at sources.redhat.com

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