From efd9ed5f579349ea991e8fe250b8e414716f543e Mon Sep 17 00:00:00 2001 From: "William A. Rowe Jr" Date: Thu, 30 May 2002 05:54:43 +0000 Subject: [PATCH] Now a moot issue. Isn't it time to just drop "PRs that have been suspended forever waiting for someone to put them into 'the next release'" if they have no status? git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95387 13f79535-47bb-0310-9956-ffa450edef68 --- STATUS | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/STATUS b/STATUS index 0245a7b5dc..063f9b74ce 100644 --- a/STATUS +++ b/STATUS @@ -1,5 +1,5 @@ APACHE 2.0 STATUS: -*-text-*- -Last modified at [$Date: 2002/05/30 05:09:24 $] +Last modified at [$Date: 2002/05/30 05:54:43 $] Release: @@ -319,6 +319,10 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: the ESC key, with a nice message) if the server died a bad death (non-zero exit code) in console mode. Resolution: bring forward same ugly hacks from 1.3.13-.20 + This is not so simple. Any exit() from APR or other libraries + can't be caught unless we add some sort of apr_exit(rv) with + registered apr_atexit() fn's that have the return code as an + argument to the registered fn. * Port of mod_ssl to Apache 2.0: @@ -901,7 +905,3 @@ Available Patches: * Dan Rench's patch to add allow the errmsg and timefmt of SSI's to be modified in the config file. Patch is available in PR6193 - -Open issues: - - * Which MPMs will be included with Apache 2.0? -- 2.40.0