nodejs20

Author SHA1 Message Date

Author	SHA1	Message	Date
T.C. Hollingsworth	ea65a91fc7	Revert "allow UTF-8 change to happen" Can't do this just yet. :-( This reverts commit `b7cebd90d1`.	2014-07-31 21:53:32 -07:00
T.C. Hollingsworth	b7cebd90d1	allow UTF-8 change to happen http://blog.nodejs.org/2014/06/16/openssl-and-breaking-utf-8-change/ I've looked into this further and I think Debian is being a bit too pedantic; not worth fighting with this patch every release. ;-)	2014-07-31 17:42:33 -07:00
T.C. Hollingsworth	50877fbc3a	new upstream release 0.10.29 http://blog.nodejs.org/2014/06/16/node-v0-10-29-stable/ - The invalid UTF8 fix has been reverted since this breaks v8 API, which cannot be done in a stable distribution release. This build of nodejs will behave as if NODE_INVALID_UTF8 was set. For more information on the implications, see: http://blog.nodejs.org/2014/06/16/openssl-and-breaking-utf-8-change/	2014-06-18 23:36:28 -07:00

T.C. Hollingsworth

ea65a91fc7

Revert "allow UTF-8 change to happen"

Can't do this just yet.  :-(

This reverts commit b7cebd90d1.

2014-07-31 21:53:32 -07:00

T.C. Hollingsworth

b7cebd90d1

allow UTF-8 change to happen

http://blog.nodejs.org/2014/06/16/openssl-and-breaking-utf-8-change/

I've looked into this further and I think Debian is being a bit
too pedantic; not worth fighting with this patch every release.  ;-)

2014-07-31 17:42:33 -07:00

T.C. Hollingsworth

50877fbc3a

new upstream release 0.10.29

http://blog.nodejs.org/2014/06/16/node-v0-10-29-stable/
- The invalid UTF8 fix has been reverted since this breaks v8 API, which cannot
  be done in a stable distribution release.  This build of nodejs will behave as
  if NODE_INVALID_UTF8 was set.  For more information on the implications, see:
  http://blog.nodejs.org/2014/06/16/openssl-and-breaking-utf-8-change/

2014-06-18 23:36:28 -07:00

3 Commits