From e3ccbedb58fac33319774f4b2160f17c295d5082 Mon Sep 17 00:00:00 2001 From: Kaspar Brand Date: Thu, 14 Nov 2013 05:46:22 +0000 Subject: [PATCH] reply to comment git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1541829 13f79535-47bb-0310-9956-ffa450edef68 --- STATUS | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/STATUS b/STATUS index 4370cbb958..f89563152d 100644 --- a/STATUS +++ b/STATUS @@ -163,6 +163,14 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK: [wrowe comments] is it possible to split the patch into 'accepted for 2.2' which is straightforward to review (and commit seperately) from those features 'new to 2.4'? I think that would attract the necessary eyeballs. + kbrand: not sure what exactly "accepted for 2.2" would mean here, basically + all these changes are enhancements, not bug fixes (and only the + latter I would consider for backporting to a "legacy branch"). + Identifying those bullets at the beginning of the 2.4.x patch + which you consider "accepted 2.2" might help / give further clues, + though it should be noted that mod_ssl in 2.4 has drifted + away from 2.2 quite somewhat meanwhile (think of the removal of + ssl_toolkit_compat.h e.g.). * mod_auth_form: Make sure the optional functions are loaded even when the AuthFormProvider isn't specified.