I have no earthly idea what this comment is referring to. Nuke it.

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

diff --git a/modules/filters/mod_include.c b/modules/filters/mod_include.c
index 4edf13aeec5963ec8a4d531a04335f34112ea45e..311c61e64a10e2611db6ccf1012af86735c70d30 100644 (file)
--- a/modules/filters/mod_include.c
+++ b/modules/filters/mod_include.c
@@ -3353,12 +3353,6 @@ static apr_status_t includes_filter(ap_filter_t *f, apr_bucket_brigade *b)
         ap_add_cgi_vars(r);
         add_include_vars(r, conf->default_time_fmt);
     }
-    /* XXX: this is bogus, at some point we're going to do a subrequest,
-     * and when we do it we're going to be subjecting code that doesn't
-     * expect to be signal-ready to SIGALRM.  There is no clean way to
-     * fix this, except to put alarm support into BUFF. -djg
-     */
-
     /* Always unset the content-length.  There is no way to know if
      * the content will be modified at some point by send_parsed_content.
      * It is very possible for us to not find any content in the first