CI: https://ci.nodejs.org/job/node-test-pull-request/2872/
Release test: https://nodejs.org/download/test/v4.4.6-test2016053100b2963392da67ec47ff79dfc8fed6a54ddc2d93/
(release job running in release server as 932)

Let's leave 0.10 and 0.12 alone, we've tried to keep the dist directories fairly static and there's already some .pdb stuff in there anyway.

I'm fine with this for v4.x but would much rather wait till we've had a few releases of v6 to verify that we've got it sorted out first.

This looks like a straightforward backport without anything different from the original, is that correct @joaocgreis? If so, lgtm.

This looks like a straightforward backport without anything different from the original

@rvagg that is correct.

I'm ok with waiting. This is ready to go in, but there's no reason to rush. I'll rebase and ping when there are a couple of releases of v6 out with this.

thanks @joaocgreis

@joaocgreis looks like this needs a rebase

Rebased. Should we start another test build?

Ci: https://ci.nodejs.org/job/node-test-pull-request/3186/

CI green, here is another test build: https://nodejs.org/download/test/v4.4.8-test20160707c21b63cbf0770fcf0b9e4a4fbe160d6eb87bfd3e/

@rvagg @thealphanerd LGTY? (and should I land this myself?)

lgtm pending an RC or test build

landed in b69bcaf

This will be included in the v4.5.0 rc's that will be put together soon