From: Eric Covener <covener@apache.org>
Date: Wed, 16 Apr 2014 01:31:30 +0000 (+0000)
Subject: withdraw -0 and promote
X-Git-Tag: 2.4.10~338
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=15e050a850317db37123e2dcd189de323ed02c6d;p=apache

withdraw -0 and promote


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

diff --git a/STATUS b/STATUS
index 30ca109bf4..866a43748b 100644
--- a/STATUS
+++ b/STATUS
@@ -100,25 +100,16 @@ RELEASE SHOWSTOPPERS:
 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
   [ start all new proposals below, under PATCHES PROPOSED. ]
 
- 
-
-PATCHES PROPOSED TO BACKPORT FROM TRUNK:
-  [ New proposals should be added at the end of the list ]
-
-  * mod_auth_form: Make sure the optional functions are loaded even when
+   * mod_auth_form: Make sure the optional functions are loaded even when
     the AuthFormProvider isn't specified. PR 56351.
     trunk patch: https://svn.apache.org/r1531672
     2.4.x patch: trunk patch works, modulo CHANGES
     +1: minfrin, jim, ylavic
-    -0 covener: does that mean just loading mod_auth_form w/o mod_request 
-                and mod_filter now causes a post-config failure?
-    minfrin: It does, however it would only affect configs where mod_auth_form
-             has been loaded but not used, as any attempt to use mod_auth_form
-             without mod_request and mod_session present would cause the very
-             same failure. Would a warning in the release notes be good enough?
-    ylavic: It fixes a runtime crash in this situation (PR 56351), I think
-            post_config (startup) is the best choice => +1
- 
+
+PATCHES PROPOSED TO BACKPORT FROM TRUNK:
+  [ New proposals should be added at the end of the list ]
+
+
    * mod_slotmem_shm: Remove wonky and dangerous code that knows about APR
      internals. We work fine w/o it anyway at this stage.
      trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1561385