On 2014/03/26 04:33:12, trevnorris wrote:
Reason for this backport is because Node.js will be releasing v0.12 stable
soon,
and will be tied to the 3.24.35 branch for the duration of that cycle.
This patch is very useful and it would be preferable it lands directly in
v8
instead of Node needing to float a patch.
While I understand that this might be useful for Node, I think it is
already far
to late to back-merge something. Chrome 34 will be out in roughly 2 weeks
IIRC,
and only important security fixes will be back-merged now. For everything
else,
the risk simply is too high, especially for such a cross-cutting CL.
Leaving the final word for Danno...
https://codereview.chromium.org/211393007/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
