Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Tue, 11 Sep 2001 18:55:09 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Unclear on pthreads status -- release 1.3.3?
Message-ID: <20010911185509.A32569@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20010911110428 DOT A12673 AT redhat DOT com> <1000248252 DOT 30279 DOT 1 DOT camel AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1000248252.30279.1.camel@lifelesswks>
User-Agent: Mutt/1.3.21i

On Wed, Sep 12, 2001 at 08:44:08AM +1000, Robert Collins wrote:
>On Wed, 2001-09-12 at 01:04, Christopher Faylor wrote:
>> I'm ready to release 1.3.3 but it seems like the final reports for
>> pthreads are not yet in.
>
>Other than the report of a problem with broadcast() I'm happy with the
>results. If you can delay for day or so while I find out if more details
>on that, then I have 2 final changes to commit: 1) the critical section
>change I posted here before, and 2) get rid of the api_fatal() calls and
>replace with just handle it silently, guessing at correctness. 

FWIW, I forced a snapshot so your stuff is available at
http://cygwin.com/snapshots/ .

Let me reiterate that I REALLY want to release 1.3.3 ASAP.

cgf