We really think such bug fixes should be ported to CURRENT STABLE build, before the newly stable version is out. Because people are not recommended to work on unstable builds for productions, but current stable wouldn't get fixed. Then all we can do is wait? :-) Well, if the porting is tough due to differences between 0.7 and 0.6, then forget this ;-)
Regards, Mophy On Feb 7, 3:01 am, Igor Zinkovsky <izinkov...@gmail.com> wrote: > I believe this was fixed in master (https://github.com/joyent/node/ > commit/e6b6075024e9f1330575b10d7e6552e1ea6dad56), but will not be back- > ported to v0.6. Latest unstable build (v0.7.2) should contain the fix. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
