Return-Path: Delivered-To: apache-cvs-archive@hyperreal.org Received: (qmail 27877 invoked by uid 6000); 5 Oct 1998 23:04:31 -0000 Received: (qmail 27871 invoked by alias); 5 Oct 1998 23:04:30 -0000 Delivered-To: apache-1.3-cvs@hyperreal.org Received: (qmail 27869 invoked by uid 125); 5 Oct 1998 23:04:29 -0000 Date: 5 Oct 1998 23:04:29 -0000 Message-ID: <19981005230429.27868.qmail@hyperreal.org> From: jim@hyperreal.org To: apache-1.3-cvs@hyperreal.org Subject: cvs commit: apache-1.3 STATUS Sender: apache-cvs-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org jim 98/10/05 16:04:29 Modified: . STATUS Log: Remove some out-of-date comments Revision Changes Path 1.502 +1 -13 apache-1.3/STATUS Index: STATUS =================================================================== RCS file: /export/home/cvs/apache-1.3/STATUS,v retrieving revision 1.501 retrieving revision 1.502 diff -u -r1.501 -r1.502 --- STATUS 1998/10/05 22:34:28 1.501 +++ STATUS 1998/10/05 23:04:28 1.502 @@ -97,13 +97,6 @@ documentation... we should handle it in the case the user doesn't ever supply a dot-notation address. - * Amdahl UTS 2.1.2 - Message-Id: <9801211635.ZM7239@ihgp1.ih.lucent.com> - Message-Id: <199801220935.BAA13813@tiber.cisco.com> - Jim: Sounded like the version of the OS that required - the patches were WAY old and would bugger the newer - versions... Not sure if we want to do that. - * Problems dealing with .-rooted domain names such as "twinlark." versus "twinlark.arctic.org.". See the thread containing Message-ID: <19980203211817.06723@deejai.mch.sni.de> for more details. @@ -155,7 +148,7 @@ of: alpha bebox macppc newsmips ofppc pica pmax sparc64. * How should an Apache binary release tarball look? - NOTE: This should be resolved before 1.3.1 !! + NOTE: This should be resolved before 1.3.3 !! 1. The "old" way where it is just a source release tarball plus a pre-compiled src/httpd-. It is created @@ -275,11 +268,6 @@ * In ap_bclose() there's no test that (fb->fd != -1) -- so it's possible that it'll do something completely bogus when it's used for read-only things. - Dean Gaudet - - * ap_pcfg_openfile doesn't use pfopen() to open the file. Consider - .htaccess parsing, if a timeout occurs the file may not be closed. I - can't imagine that a timeout would be set during this stage... but it'd - probably be good to just clean this up. - Dean Gaudet * Okay, so our negotiation strategy needs a bit of refinement. See .