| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Are we fine with retroactively changing the changelog like this?
Sorry, something went wrong.
There was a problem hiding this comment.
I'm not really sure it matters either way.
Sorry, something went wrong.
There was a problem hiding this comment.
No one's going to read that anyways, that's for sure. I'm feeling adding to the changelog after the release isn't quite right. Let's remove it.
Sorry, something went wrong.
There was a problem hiding this comment.
Intention from #3258 (comment) but I still need to do a PR for new.nodejs.org
Sorry, something went wrong.
There was a problem hiding this comment.
I see. Still, I think the changelog train has left here.
To avoid such issues in the future: How about we add a relnotes label so people can tag changes that they feel worthy of being mentioned in a release? cc: @nodejs/release.
Sorry, something went wrong.
There was a problem hiding this comment.
+1 on the relnotes label. I'm -1 on making this particular change tho.
Sorry, something went wrong.
|
Given the -1's on merging this, I'm inclined to close. Can open if someone feels it's necessary. |
Sorry, something went wrong.
|
@jasnell those were only for the changelog bit. The doc part is important. Reopening. |
Sorry, something went wrong.
|
Ah, right, completely forgot that the PR had the doc changes. @skomski if you can update the PR to just include the doc change that would be helpful |
Sorry, something went wrong.
There was a problem hiding this comment.
This should be buf.indexOf(value[, byteOffset[, encoding]]). If not then the implementation is wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Actually, since typeof byteOffset === 'number' and typeof encoding === 'string' the arguments should actually be indexOf(value[, byteOffset][, encoding]). Sorry about that.
Sorry, something went wrong.
|
@skomski ... ping... did you see the comments from @trevnorris ? |
Sorry, something went wrong.
|
Updated. |
Sorry, something went wrong.
|
Thanks. I'll land this after #4803. I incorrectly believed that byteOffset was completely optional. That PR is a fix. |
Sorry, something went wrong.
There was a problem hiding this comment.
Is this amount of linebreaks really necessary?
Sorry, something went wrong.
PR-URL: #3373 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
|
Landed with whitespace changes, and made example match existing pattern, in 2bcea02. Thanks much! |
Sorry, something went wrong.
PR-URL: #3373 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
|
@trevnorris this is not landing cleanly into the lts branch. We will likely need to see the changes from #4370 ported over before this can land. |
Sorry, something went wrong.
PR-URL: #3373 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
PR-URL: #3373 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
PR-URL: #3373 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
PR-URL: nodejs#3373 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
| Back | FazBrowse Home | New Git URL |
No description provided.