Skip to content

Conversation

@sam-github
Copy link
Contributor

@sam-githubsam-github commented Jul 21, 2017

backport of docs from #13531

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

doc

@nodejs-github-botnodejs-github-bot added doc Issues and PRs related to the documentations. net Issues and PRs related to the net subsystem. v6.x labels Jul 21, 2017
Backport of the documentation from nodejs#13531 that did not land in 2fb1381. PR-URL: nodejs#13553 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: James M Snell <[email protected]>
@sam-githubsam-githubforce-pushed the v6.x-backport-13531-docs branch from c832efa to 3dd5282CompareJuly 21, 2017 17:10
@sam-github
Copy link
ContributorAuthor

@MylesBorins @nodejs/lts I'm not sure what the metadata should be. I left the metadata from the original PR in the commit, but that seems weird.

Have we agreed on a scheme for what metadata should look like on backport PRs?

@MylesBorins
Copy link
Contributor

@sam-github we agreed to keep all original meta data (including reviews) and add a new field backport-pr-url

@MylesBorins
Copy link
Contributor

I've gone ahead and rebased this back into the original cherry-pick 59eb761

@gibfahngibfahn reopened this Jul 22, 2017
@gibfahn
Copy link
Member

My bad @MylesBorins, didn't realise you meant you'd rebased and landed on v6.x-staging.

@gibfahngibfahn closed this Jul 22, 2017
@sam-githubsam-github deleted the v6.x-backport-13531-docs branch October 16, 2018 17:06
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docIssues and PRs related to the documentations.netIssues and PRs related to the net subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@sam-github@MylesBorins@gibfahn@refack@nodejs-github-bot