Skip to content

Conversation

@techjeffharris
Copy link
Contributor

The description for statusMessage was accidentally moved under the
heading for http.IncomingMessage.socket. This commit puts it back
in the correct place.

/CC @nodejs/http @nodejs/documentation

Fixes: #4558

The description for `statusMessage` was accidentally moved under the
heading for `http.IncomingMessage.socket`.  This commit puts it back
in the correct place.

see: nodejs#4558
@jasnell
Copy link
Member

jasnell commented Jan 23, 2016

LGTM

@jasnell jasnell added doc Issues and PRs related to the documentations. lts-watch-v4.x labels Jan 23, 2016
@mscdex mscdex added the http Issues or PRs related to the http subsystem. label Jan 23, 2016
@r-52
Copy link
Contributor

r-52 commented Jan 23, 2016

LGTM

@silverwind
Copy link
Contributor

Thanks! Landed in f19b9d6.

silverwind pushed a commit that referenced this pull request Jan 24, 2016
The description for `statusMessage` was accidentally moved under the
heading for `http.IncomingMessage.socket`.  This commit puts it back
in the correct place.

PR-URL: #4822
Fixes: #4558
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Klauke <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
@silverwind silverwind closed this Jan 24, 2016
rvagg pushed a commit that referenced this pull request Jan 25, 2016
The description for `statusMessage` was accidentally moved under the
heading for `http.IncomingMessage.socket`.  This commit puts it back
in the correct place.

PR-URL: #4822
Fixes: #4558
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Klauke <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
@abdulhannanali
Copy link

LGTM!

benjamingr pushed a commit to benjamingr/io.js that referenced this pull request Jan 27, 2016
The description for `statusMessage` was accidentally moved under the
heading for `http.IncomingMessage.socket`.  This commit puts it back
in the correct place.

PR-URL: nodejs#4822
Fixes: nodejs#4558
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Klauke <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 17, 2016
The description for `statusMessage` was accidentally moved under the
heading for `http.IncomingMessage.socket`.  This commit puts it back
in the correct place.

PR-URL: #4822
Fixes: #4558
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Klauke <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 18, 2016
The description for `statusMessage` was accidentally moved under the
heading for `http.IncomingMessage.socket`.  This commit puts it back
in the correct place.

PR-URL: #4822
Fixes: #4558
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Klauke <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Feb 18, 2016
MylesBorins pushed a commit that referenced this pull request Mar 2, 2016
The description for `statusMessage` was accidentally moved under the
heading for `http.IncomingMessage.socket`.  This commit puts it back
in the correct place.

PR-URL: #4822
Fixes: #4558
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Klauke <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
scovetta pushed a commit to scovetta/node that referenced this pull request Apr 2, 2016
The description for `statusMessage` was accidentally moved under the
heading for `http.IncomingMessage.socket`.  This commit puts it back
in the correct place.

PR-URL: nodejs#4822
Fixes: nodejs#4558
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Roman Klauke <[email protected]>
Reviewed-By: Roman Reiss <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to the documentations. http Issues or PRs related to the http subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants