Replace 'Fork me at Github' ribbon with a new one fitting the website's color
scheme.

NULL-MD5 is not always compiled into openssl but RC4-MD5 should always be
available.

Fixes #3531.

The gcc 4.5.x have various bugs that make V8 crash in various and interesting
ways when -fstrict-aliasing is in effect.

We already enable -fstrict-aliasing when gcc >= 4.6.0 but let's enable it for
gcc < 4.5.0 as well. The aliasing bugs that we ran into in the past are all
particular to the 4.5.x releases.

For some reason, though, it looks like EnvGetter is not called for the
key `__proto__`, so I can't make the info->Data() accessible.  However,
putting the Object.prototype keys there, in such a way that they are not
OwnProperties, and are supersceded by environs, makes process.env much
less weird.

The test failed when a router replies IPADDR_BROADCAST.
Fixed it by specifying only one address to bind a socket.

This reverts commit 6d98524.
This reverts commit 60ff789.

closure_linter now depends on the gflags module and not everyone will have that
installed by default.

The reverted commit caused a v8 assertion to trigger in debug mode.
This reverts commit e307468.

The V8 assert got triggered by a missing HandleScope::Close().

Conflicts:
	configure
	src/node_version.h

If the command entered is exactly the same as the last history item,
don't dupe it in the history

Compile OpenSSL with inline assembly for big numbers

Speeds up benchmark/settimeout.js by about 30%.

Conflicts:
	src/node_version.h

Fix #3616

Conflicts:
	deps/npm

This is rewrite of #3701 and #3603 before.

This patch introduce `util.inspect.styles`
and `util.inspect.colors` objects, which enables customization
of color sequences.

When there is an error that is thrown in a nextTick function, which is
then handled by a domain or other process.on('uncaughtException')
handler, if the error handler *also* adds a nextTick and triggers
multiple MakeCallback events (ie, by doing some I/O), then it would
skip over the tickDepth check, resulting in an infinite spin.

Solution: Check the tickDepth at the start of the tick processing, and
preserve it when we are cleaning up in the error case or exiting early
in the re-entry case.

In order to make sure that tick callbacks are *eventually* handled, any
callback triggered by the underlying spinner in libuv will be processed
as if starting from a tick depth of 0.

Conflicts:
	src/node_version.h

It's useful for passing some additional options of request object to the
underlying API

socket.authorizationError should always be string. Also make sni test
pass.

This reverts commit 53716eb.

And fix last failing tests

* punycode: update to v1.1.1 (Mathias Bynens)

* c-ares: upgrade to 1.9.0 (Saúl Ibarra Corretgé)

* dns: ignore rogue DNS servers reported by windows (Saúl Ibarra Corretgé)

* unix: speed up uv_async_send() (Ben Noordhuis)

* darwin: get cpu model correctly on mac (Xidorn Quan)

* nextTick: Handle tick callbacks before any other I/O (isaacs)

* Enable color customization of `util.inspect` (Pavel Lang)

* tls: Speed and memory improvements (Fedor Indutny)

* readline: Use one history item for reentered line (Vladimir Beloborodov)

* Fix #3521 Make process.env more like a regular Object (isaacs)