Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 88303 invoked by uid 500); 12 Nov 2001 00:20:13 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 88292 invoked from network); 12 Nov 2001 00:20:12 -0000 X-Authentication-Warning: cobra.cs.Virginia.EDU: jcw5q owned process doing -bs Date: Sun, 11 Nov 2001 19:20:15 -0500 (EST) From: Cliff Woolley X-X-Sender: To: Subject: Re: 2.0.29? (Re: apparent mod_cgid bug Re: Two apache/2.0.29-dev problems) In-Reply-To: <20011111234227.04F6446DFD@koj.rkbloom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sun, 11 Nov 2001, Ryan Bloom wrote: > > - fix infinite loop in mod_cgid > > - fix segfault in prefork > > - fix build problems on Win32 (mktemp) > > - fix multithreading problem on BSDi (-D_REENTRANT) > > - fix file cleanup problems in apr_proc_create > Stop tagging 2.0.28. Half the changes above have nothing to do with bugs > in the server. They are new features or improvements in the code. Of course. I never said the whole thing should be retagged. Those first two above would be really nice to have fixed, and the next three would be kinda nice, but aren't crucial AFAIK. But in any event, with or without these things, > Just release 2.0.28 already. +1. --Cliff -------------------------------------------------------------- Cliff Woolley cliffwoolley@yahoo.com Charlottesville, VA