Return-Path: Delivered-To: apmail-apache-cvs-archive@apache.org Received: (qmail 37105 invoked by uid 500); 25 May 2000 23:30:00 -0000 Mailing-List: contact apache-cvs-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-cvs@apache.org Received: (qmail 37094 invoked by uid 500); 25 May 2000 23:30:00 -0000 Delivered-To: apmail-apache-2.0-cvs@apache.org Date: 25 May 2000 23:29:59 -0000 Message-ID: <20000525232959.37090.qmail@locus.apache.org> From: rbb@locus.apache.org To: apache-2.0-cvs@apache.org Subject: cvs commit: apache-2.0 STATUS rbb 00/05/25 16:29:59 Modified: . STATUS Log: This item doesn't really work properly, so we are removing it from the STATUS file. I was going to wait, but Manoj (the person who originally put it in STATUS) said get rid of it, so away it goes. Revision Changes Path 1.69 +1 -3 apache-2.0/STATUS Index: STATUS =================================================================== RCS file: /home/cvs/apache-2.0/STATUS,v retrieving revision 1.68 retrieving revision 1.69 diff -u -r1.68 -r1.69 --- STATUS 2000/05/25 16:45:28 1.68 +++ STATUS 2000/05/25 23:29:59 1.69 @@ -1,5 +1,5 @@ Apache 2.0 STATUS: -Last modified at [$Date: 2000/05/25 16:45:28 $] +Last modified at [$Date: 2000/05/25 23:29:59 $] Release: @@ -48,8 +48,6 @@ CRT calls or do we need to add region locking each time we access the logs? Status: - - * The handler hook needs to use the new registration system * We need a thread-safe resolver, at least on Unix. Status: The best known candidate would be something from