The argument that this is a reversion to the httpd/access/srm

	multifile scenario is bogus, IMHO; the problem with those
	was that their purposes were not clear, nor were the orders
	of invocation.  Putting massive (or tiny but uncommon) chunks
	of easily self-contained special-function directives into
	separate files simplifies the basic configuration and doesn't
	revert to either of the trinity-file complaints, since these
	would need to be explicitly invoked with an Include directive.

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

diff --git a/STATUS b/STATUS
index c313d0a3113ff6e8beb5a087373c47057ccf415c..dceb73123fb50c9467af4e931615820f8b6e9102 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                             -*-text-*-
-Last modified at [$Date: 2001/10/17 00:58:32 $]
+Last modified at [$Date: 2001/10/17 14:50:48 $]
 
 Release:
 
@@ -35,7 +35,7 @@ on related projects:
 RELEASE SHOWSTOPPERS:
 
     * The recent split of proxy.conf and ssl.conf, good or bad?
-        Split ssl.conf & proxy.conf: +1 OtherBill, Aaron
+        Split ssl.conf & proxy.conf: +1 OtherBill, Aaron, Ken
         Split out ssl.conf only:     +1 Ryan, BrianH
         Everything in httpd.conf:    +1 Cliff, Justin