Joe Orton wrote:
at least some of these problems will at require API changes to fix, so it seems dumb to ship as-is.
so -- you are suggesting deferring these into 1.4.0?
I would (again) suggest moving this stuff out onto a branch so those interested in making it work can do so without getting in the way of releases.
i've made it so; branches/1.3.x now exist for each of apr and apr-util.
