> Cool. I believe something is better than nothing :). > > (I'm sure you're already aware of this - but thought it'd be better to let > you know) > I believe my patch went into r1.127 - and has been labelled for the 2.0.40 > release. So, you might want to bump the label before it's released.
It has already been released. And where did the three +1 come from anyway? That is still required on the tarball (not the tag) before the announcement is supposed to go out, even for security releases. 2.0.40 will fail to compile for future releases of OpenSSL 0.9.x except for those that also happen to end in e-z or are specifically asked for via the --with-ssl=DIR option in configure. Maybe that could go on the "known bugs" page. I have no idea why the patch was applied just prior to the tag. ....Roy
