On Mon, May 19, 2014 at 6:54 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> Ok, then please update the RFC with what you see as the way forward,
> including adding actual memory impacts to it and restart the vote when
> the RFC is ready.
Asking us, after months of discussions, work, tests, publications,
etc. to do change that could be done post acceptation easily, as it is
always the case for any change affecting more than a couple of LoC.
And with which guarantee? So far none, even the contrary, all
possible ways are used too block this RFC, while we keep trying to
find compromises and keep helping phpng moving forward in the
meantime. I hope you can understand that I have hard time to justify
more efforts on this patch at this stage, we are not an endless free
resource.
At some point trust, compromise and common sense must be followed. And
we are at this point here. We said numerous time on this list and IRC
what are the goals and what are the possibilities of improving both
the 64bit patch and phpng in the coming months/years. Let end this
unproductive debate and let us back to code, for the good of PHP.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org