Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: 19 Feb 2003 07:21:44 -0000
Message-ID: <20030219072144.69700.qmail@icarus.apache.org>
From: jerenkrantz@apache.org
To: httpd-2.0-cvs@apache.org
Subject: cvs commit: httpd-2.0 STATUS

jerenkrantz    2003/02/18 23:21:44

  Modified:    .        STATUS
  Log:
  Start tracking the PRs for known RFC 2616 violations.  (Note that the test
  cases in the PR are ridiculously hard to follow.)
  
  These tend to be primarily in caching/proxy, but some are in the core.
  
  Revision  Changes    Path
  1.758     +9 -1      httpd-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/STATUS,v
  retrieving revision 1.757
  retrieving revision 1.758
  diff -u -u -r1.757 -r1.758
  --- STATUS	18 Feb 2003 21:06:15 -0000	1.757
  +++ STATUS	19 Feb 2003 07:21:43 -0000	1.758
  @@ -75,6 +75,14 @@
   
   RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
   
  +    * RFC 2616 violations.
  +      Closed PRs: 15857.
  +      Open PRs: 15852, 15859, 15861, 15864, 15865, 15866, 15868, 15869,
  +                15870, 16120, 16125, 16126, 16133, 16135, 16136, 16137,
  +                16138, 16139, 16140, 16142, 16518, 16520, 16521, 
  +      jerenkrantz says: need to decide how many we need to backport and/or
  +                        if these rise to showstopper status.
  +
       * There is a bug in how we sort some hooks, at least the pre-config
         hook.  The first time we call the hooks, they are in the correct 
         order, but the second time, we don't sort them correctly.  Currently,