Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Thu, 20 Apr 2000 17:48:47 -0400
Message-Id: <200004202148.RAA02429@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <20000420174522.A3446@cygnus.com> (message from Chris Faylor on
	Thu, 20 Apr 2000 17:45:22 -0400)
Subject: Re: Sigh.  First cygwin show stopper?
References: <20000420173420 DOT A3286 AT cygnus DOT com> <200004202142 DOT RAA02338 AT envy DOT delorie DOT com> <20000420174522 DOT A3446 AT cygnus DOT com>


> Just signal.

Doesn't sound like it needs an immediate fix, then.  If people
complain between now and our next update, we can point them at the
snapshots as an interim solution.

We're gonna get a bunch of stuff like this, just because it's a new
release.  Save them up and release them all at once.  It also means
take it easy on cvs - we can't destabilize it for a week or two, until
we do the 1.1.1 bugfix release.