httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br...@hyperreal.org
Subject cvs commit: apache-1.3 STATUS
Date Sat, 09 May 1998 00:17:39 GMT
brian       98/05/08 17:17:39

  Modified:    .        STATUS
  Log:
  garbage in, garbage out :)  removed the whole server string thing, added
  two items from the list so we don't forget.
  
  Revision  Changes    Path
  1.390     +7 -14     apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.389
  retrieving revision 1.390
  diff -u -r1.389 -r1.390
  --- STATUS	1998/05/08 21:53:25	1.389
  +++ STATUS	1998/05/09 00:17:38	1.390
  @@ -134,20 +134,6 @@
   
   Open issues:
   
  -    * What do to about SERVER_SUBVERSION now?
  -      STATUS:
  -       o Scrap it now that modules can use ap_add_version_component
  -         Jim +1 (make sure this is clear :) ), Brian +1, Ken +1
  -      Dean: -1, and I am also vetoing the new AddVersionComponent
  -	directive.  My reason is: if a module is "significant" then
  -	it will ap_add_version_component(); if a patch is
  -	"significant" then it can modify SERVER_SUBVERSION.  There are
  -	no other *code* changes possible that the admin should be
  -	noting.  If folks really want to play the customized server
  -	version game they can recompile, or build a module to do it.
  -	If we put it in the default server we'll end up seeing lots of
  -	funny (read: annoying) false things start to appear.
  -
       * Paul would like to see a 'gdbm' option because he uses
         it a lot.
   
  @@ -304,6 +290,11 @@
       * signal type handling
       	- how to rotate logs from command line?
   
  +    * Currently if you double click on the conf files or the
  +      log files you get a useless dialog offering the set of all
  +      execuables, usually after a very long pause.  Ought
  +      to stuff .conf in the registry mapping it to text.
  +
   Delayed until after 1.3.0, unless someone happens to get to it:
   
       * Arnt Gulbrandsen <agulbra@troll.no> 03 Apr 1998 21:28:17 +0200
  @@ -352,4 +343,6 @@
           3) byte range error handling
           4) update the Accept-Encoding parser to allow q-values
           5) would be nice if the proxy used Via and Max-Forwards, even as HTTP/1.0
  +
  +    * #ifdef __EMX__ --> #ifdef OS2.
   
  
  
  

Mime
View raw message