From: Greg Ames <gregames@apache.org>
Date: Fri, 22 Mar 2002 15:05:21 +0000 (+0000)
Subject: comment on a "showstopper" which is apparantly dormant.
X-Git-Tag: 2.0.34~175
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3876dbc87a0824a647964f41e1239262831ecbbb;p=thirdparty%2Fapache%2Fhttpd.git

comment on a "showstopper" which is apparantly dormant.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@94127 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/STATUS b/STATUS
index 28297d7da92..28657897fdf 100644
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2002/03/22 14:34:13 $]
+Last modified at [$Date: 2002/03/22 15:05:21 $]
 
 Release:
 
@@ -68,6 +68,12 @@ FINAL RELEASE SHOWSTOPPERS:
         simple check in default_handler to see if dir/file_walk has
         been done (a footprint left by dir/file_walk doesn't have to
         be in request_rec; a better place is core_request_config)
+        
+        gregames says: can this happen somehow without a broken module
+            being involved?  If not, why waste cycles trying to defend against
+            potential broken modules?  It seems futile.  Please vote.
+          not a showstopper: gregames
+          showstopper:
 
     * API changes planned for 2.0 that should happen before the
       GA release: