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
Subject: Re: Unclear on pthreads status -- release 1.3.3?
From: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
To: cygwin-developers AT cygwin DOT com
In-Reply-To: <20010911110428.A12673@redhat.com>
References: <20010911110428 DOT A12673 AT redhat DOT com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.13 (Preview Release)
Date: 12 Sep 2001 08:44:08 +1000
Message-Id: <1000248252.30279.1.camel@lifelesswks>
Mime-Version: 1.0
X-OriginalArrivalTime: 11 Sep 2001 22:31:02.0680 (UTC) FILETIME=[703FD980:01C13B11]

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. 

> So, I guess I have another 24 hour wait on this?  Can anyone confirm
> or deny that Robert's changes have done the trick?

I swear, no more delays!

Rob