Merge branch 'v0.10.0-release' into v0.10
Now working on 0.10.1
blog: Post about v0.10.0
doc: events: add 'removeListener' event section

Amends commit 84221fd by (also) documenting the 'removeListener' event
in a dedicated section, like the 'newListener' event.

Fixes #4977.
blog: fix small typo in v0.10.0 release article
blog: Fix typo in typo fix
core: Unwrap without aborting in handle fd getter
net: handle 'finish' event only after 'connect'
doc: path.join() arguments must be strings

In v0.8, non-string arguments were ignored. v0.10 throws an exception.
core: Move UNWRAP_NO_ABORT to handle_wrap.h

Otherwise it cannot be used in StreamWrap.

Forgot to include in last patch, broke the build.
stream: Never call decoder.end() multiple times

Fixes decoder.end() being called on every push(null). As the tls module
does this, corrupt stream data could potentially be added to the end.
doc: add note on process.title max length

Fixes #5006.
doc: implicit fs callbacks don't throw in v0.10

But they will in v0.12.

Re #5005.
fs: Missing cb errors are deprecated, not a throw

Commit a804347 makes fs function rethrow errors when the callback is
omitted. While the right thing to do, it's a change from the old v0.8
behavior where such errors were silently ignored.

To give users time to upgrade, temporarily disable that and replace it
with a function that warns once about the deprecated behavior.

Close #5005
Revert "stream: Never call decoder.end() multiple times"

This reverts commit 615d809ac684a7d2cc7ee5e1aa58f0a921b529a0.
doc: change dgram to socket for properties of dgram.Socket

Fixes #4919.
deps: upgrade libuv to 7b66ea1
net: improve arbitrary tcp socket support

Consider this example:

  // fd 3 is a bound tcp socket
  var s = net.createServer(cb);
  s.listen({ fd: 3 });
  console.log(s.address());  // prints null

This commit makes net.Server#address() print the actual address.

Ditto for non-listen sockets; properties like net.Socket#localAddress
and net.Socket#remoteAddress now return the correct value.

Fixes #5009.
http: Don't hot-path end() for large buffers

The benefits of the hot-path optimization below start to fall off when
the buffer size gets up near 128KB, because the cost of the copy is more
than the cost of the extra write() call.  Switch to the write/end method
at that point.

Heuristics and magic numbers are awful, but slow http responses are
worse.

Fix #4975
doc: don't mark fs callbacks as optional

Refs #5005, #5008