Received: by taz.hyperreal.com (8.6.12/8.6.5) id GAA09912; Thu, 14 Dec 1995 06:58:11 -0800 Received: from sierra.zyzzyva.com by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id GAA09903; Thu, 14 Dec 1995 06:58:05 -0800 Received: from zyzzyva.com (randy@localhost [127.0.0.1]) by sierra.zyzzyva.com (8.6.12/8.6.11) with ESMTP id IAA28805 for ; Thu, 14 Dec 1995 08:57:57 -0600 Message-Id: <199512141457.IAA28805@sierra.zyzzyva.com> To: new-httpd@hyperreal.com Subject: Re: Set AUTH_TYPE in CGI scripts In-reply-to: p.richards's message of Thu, 14 Dec 1995 12:20:11 +0000. <199512141220.MAA22586@cadair.elsevier.co.uk> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Dec 1995 08:57:56 -0600 From: Randy Terbush Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@apache.org > There needs to be an accessible area where patches can be retrieved by > end-users. A web page should be set up which lists known bugs in a > particular release and what patch to apply for the impatient. > > This would allow us to make patches available early on an "as is" basis > for those people who have been tripped up by the bug and need an > immediate fix. We can avoid lots of little incremental releases that way > giving us time to stress test the bug fix releases properly and to > batch the bug fix patches over a longer time period. It's been out there since we released 1.0. dist/patches What patches do we feel good about placing there? I've got time to do some testing on these today, so you'll soon see my votes.