I still think that your version is wrong wrong wrong and am tempted to veto it.
It completely invalidates what ap_set_byterange() is designed to do (set r->range) as well as removes the ability to count overlaps, non-ascends, etc… On Aug 25, 2011, at 7:11 PM, Stefan Fritsch wrote: > On Thursday 25 August 2011, Jim Jagielski wrote: >> Be my guest. commit and fix rp's concerns. > > OK, done that. Trunk r1161791 passes all tests, including the new > byterange3.t and byterange4.t. >
