-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
doc: revert backported commits #6530
doc: revert backported commits #6530
Conversation
/cc @jasnell |
Yep. Looks fine. I'm thinking at this point we should generally slow down on backporting these proactively. As the delta between master and v4 grows, it's going to become more and more important to have the author of the PR to do the porting if it's to be brought back. |
+1 to that @jasnell |
In fact, I would even go so far as to say that unless we get a backport PR, we should hold off cherry-picking the commits from here on out. /cc @nodejs/lts |
@jasnell I'd like to do one more pass of things that landed in v5... but after that I think that idea is a++ |
LGTM |
06ea404
to
7f5fdd8
Compare
This reverts changes found in daf3ef6 0943001 that incorrectly updated the docs for `path.format` PR-URL: nodejs#6530 Reviewed-By: James M Snell <jasnell@gmail.com>
7f5fdd8
to
b511c5a
Compare
This reverts changes found in daf3ef6 0943001 that incorrectly
updated the docs for
path.format
closes #6437