| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
RSLGTM % two nits
Sorry, something went wrong.
Sorry, something went wrong.
|
@gengjiawen Would you be able to rebase this and fix the conflict reported? Thanks |
Sorry, something went wrong.
|
@danbev I can fix this evening :) |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
@danbev I forced push because travis-ci found a lint issue ? Do you need to re-trigger this again ? Sorry for this inconvenience. |
Sorry, something went wrong.
|
Landed in 575e086 🎉 |
Sorry, something went wrong.
PR-URL: nodejs#26493 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
|
This does not land cleanly on v11. It seems to rely on other commits (e.g. #26306) that should be backported first. Please open a manual backport for it or change the labels accordingly. |
Sorry, something went wrong.
|
I am not familiar with backport process, how should I do it ? |
Sorry, something went wrong.
|
If a PR requires manual backports, we should first identify what code it relies upon. There are other PRs that should be backported first as the one that I pointed out. Otherwise there are more conflicts and they become worse over time. So this one should likely not be the first to be backported. @joyeecheung recently added a tool to node-core-utils that is able to identify them (see https://asciinema.org/a/221244). A backport itself is just a PR which targets the staging branches of the release line. In this case v11.x-staging instead of master. |
Sorry, something went wrong.
|
I opened a backport PR for this: #26651 |
Sorry, something went wrong.
PR-URL: nodejs#26493 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: #26493 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: #26493 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
| Back | FazBrowse Home | New Git URL |
Apply clang-tidy rule https://clang.llvm.org/extra/clang-tidy/checks/modernize-make-unique.html
And also in Item 21: Prefer std::make_unique and std::make_shared to direct use of new.
cc @addaleax @refack @bnoordhuis
Checklist