Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 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 Message-Id: <1000248733.30305.18.camel@lifelesswks> Mime-Version: 1.0 X-Mailer: Evolution/0.13 (Preview Release) Date: 12 Sep 2001 08:54:13 +1000 X-OriginalArrivalTime: 11 Sep 2001 22:41:17.0474 (UTC) FILETIME=[DEB1F820:01C13B12] 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