-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
process: reintroduce ares to versions #9191
Conversation
ares version info was accidentally removed in c80f8fa. PR-URL: nodejs#347 Reviewed-By: Fedor Indutny <fedor@indutny.com>
Since I cherry-picked, the commit has the original commit message. Let me know if I should reword it. cc @jbergstroem (since it was originally your fix 😄 ) |
Does this qualify as a change that should go into a maintenance branch? |
Good question. It's there in |
we can out it in staging and include it in a future release if we need to On Wed, Oct 19, 2016, 9:22 PM Richard Lau notifications@github.com wrote:
|
Is this actually important to anyone? |
@Fishrock123 consistency, perhaps. |
Change LGTM, no strong opinions on whether it needs to be added back in. Is there any downside to including it in the next v0.12 release? |
PR-URL: #9191 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Landed in v0.12-staging with 0cdf344 |
PR-URL: nodejs/node#9191 Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Checklist
make -j8 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
process
Description of change
process.versions.ares
is missing in v0.12.17 (and earlier v0.12.x):Fixed by cherry-picking 01736dd (reference #347)