add a note about surprises ;-)

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

diff --git a/STATUS b/STATUS
index 7386468070cccaa4a4b3d0c8d870522d5316afac..bedb6060d69d9fe5286eefc500ef275331cd90d9 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2003/05/13 19:19:30 $]
+Last modified at [$Date: 2003/05/13 20:11:24 $]
 
 Release:
 
@@ -239,6 +239,12 @@ PATCHES TO PORT FROM 2.1
                   I'm quite happy to do that but don't think that should 
                   affect backporting this fix.
 
+          nd: Actually I see no problem with surprises. If someone uses this
+              tailored example config, it's probably his first SSL config. If
+              it's not his first one, he probably doesn't care about - IMHO :)
+              An appropriate change-log entry should warn the rest of the
+              people, shouldn't it?
+
     * mod_log_config: be able to log the id of the thread that handled
       the request
       modules/loggers/mod_log_config.c: r1.102-1.104