axe the discussion on the possibility of backporting

the remaining DefaultRuntimeDir functionality to the
2.4.x branch in a way that doesn't break existing
configs; the most recent info is on the dev list anyway

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

diff --git a/STATUS b/STATUS
index 2a9d361cf0f544c34565def42618fa0f0876be06..86daf40fdb45af2a7afc6d3d006bb62588f7ae33 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -222,29 +222,6 @@ OTHER PROPOSALS
      http://people.apache.org/~rjung/patches/possible-backports-httpd-trunk-2_4.txt
      If you want to propose one of those, please add them above.
 
-   * opinion on more complete DefaultRuntimeDir use in 2.4.x?
-     o If a module has a config directive for the run-time file that
-       treats the configured path as relative to server root, preserve
-       that behavior but change the location when not configured to
-       respect DefaultRuntimeDir.  With these changes, users with no
-       per-runtime-file configuration directives can control
-       everything with DefaultRuntimeDir.
-       BUT: Existing users of DefaultRuntimeDir might get a short-term scare
-       when some unconfigured run-time file starts respecting their
-       DefaultRuntimeDir directive after an upgrade.
-       +1: trawick, jim, rjung
-       rjung: applicable trunk revisions WITHOUT the compatibility tweaks
-              described above:
-          scoreboard         r1369477
-          core/pid file      r1369808
-          core/mutex         r1370288
-          mod_socache_XXX    r1370225, r1407385
-          mod_ldap           r1371684
-          mod_cache          r1407381
-          mod_slotmem_plain  r1370763
-        igalic: We have three votes, what's the status here?
-       Independently, backport any doc tweaks to 2.4 API migration page.
-
 PATCHES/ISSUES THAT ARE STALLED
 
   * mod_proxy: support Unix domain sockets /* ON HOLD */