httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@hyperreal.org
Subject cvs commit: apache-2.0 STATUS
Date Fri, 06 Feb 1998 02:58:40 GMT
coar        98/02/05 18:58:40

  Modified:    .        STATUS
  Log:
  	Tra la la..
  
  Revision  Changes    Path
  1.7       +10 -9     apache-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-2.0/STATUS,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- STATUS	1998/02/06 02:35:12	1.6
  +++ STATUS	1998/02/06 02:58:40	1.7
  @@ -21,35 +21,36 @@
   
   Open issues:
   
  -  Replace the current Unix compilation model (Configuration.tmpl, home-brew
  +  * Replace the current Unix compilation model (Configuration.tmpl, home-brew
       Configure script) with the "autoconf toolset".
  -  Status: Brian +1, Roy +1, Dean +1
  +	Status: Brian +1, Roy +1, Dean +1
   
  -  Investigate replacing the current Unix compilation model (Configuration.tmpl
  +  * Investigate replacing the current Unix compilation model (Configuration.tmpl
       home-brew Configure script) with the "autoconf toolset". (this
       varies from the above such that if it's shown that the "autoconf
       toolset" can do what we want, with less headache than what we
       have, then we go for it)
  -  Status: Jim +1
  +	Status: Jim +1, Ken +1
   
  -  The "autoconf toolset" should include all three: autoconf, automake, and 
  +  * The "autoconf toolset" should include all three: autoconf, automake, and 
       libtool.
  -  Status: Brian +1, Jim +1, Roy +1, Dean +1
  +	Status: Brian +1, Jim +1, Roy +1, Dean +1, Ken +1
   
     FEATURE SET FOR 2.0
  -  Here, we decide how many of the following feature ideas we will set for
  +    Here, we decide how many of the following feature ideas we will set for
       ourselves as work items for 2.0.  We can't do everything we would want
       to, otherwise 2.0 will never be released.  So please try and be 
       conservative with your votes.  Items in no particular order.  Feel free
       to add more, but try not to duplicate earlier items too much.
   
       a) multithreading.  
  -       Brian +1
  +       Brian +1, Ken +1
    
       b) new layered I/O.
  -       Brian +1
  +       Brian +1, Ken +1
   
       c) radically revamped API
  +       Ken +1
      
       d) just new API phases
          Brian +1
  
  
  

Mime
View raw message