Folks, this is becoming a problem with change and commit log messages,

this is not the only recent offender or offense.

  * byterange: Range of '0-' returns 206.

Please convey sense of direction in the dimension of time?  Was this

  * byterange: Range of '0-' now returns 206.

or

  * byterange: Correct erronious return values of 206 for Range '0-'.

kthxbye

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x@1201000 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/STATUS b/STATUS
index a132f4ab169402e34e5a345b436161375845997b..ebd177df9b5fb32514a0bd2cb039abae1a203be6 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -120,7 +120,7 @@ RELEASE SHOWSTOPPERS:
     2.2.x patch: http://svn.apache.org/viewvc?view=revision&revision=1177080
     2.2.x patch: http://svn.apache.org/viewvc?view=revision&revision=1177081
     2.0.x patch: http://people.apache.org/~jim/patches/2.0-byterange0-.txt
-    +1: jim, rjung
+    +1: jim, rjung, wrowe
 
   * Backport jorton's work on backstopping unrooted URI's (regex protection)
     and any mod_rewrite example corrections.