This repository was archived by the owner on Apr 22, 2023. It is now read-only.
_http_server.js: fix typo in comment#25472
Closed
devonharvey wants to merge 1 commit intonodejs:masterfrom
devonharvey:devonharvey-patch-1
Closed
_http_server.js: fix typo in comment#25472devonharvey wants to merge 1 commit intonodejs:masterfrom devonharvey:devonharvey-patch-1
devonharvey wants to merge 1 commit intonodejs:masterfrom
devonharvey:devonharvey-patch-1
Conversation
Fix misspelling of 'response' on line 453
|
LGTM |
jasnell
pushed a commit
that referenced
this pull request
Jun 4, 2015
Fix misspelling of 'response' on line 453 Reviewed-By: James M Snell <jasnell@gmail.com> PR-URL: #25472
Member
|
Landed in 016ff77 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix misspelling of 'response' on line 453 of _http_server.js
BEFORE:
// When we're finished writing the response, check if this is the last
// respose, if so destroy the socket.
AFTER:
// When we're finished writing the response, check if this is the last
// response, if so destroy the socket.
No other changes were made.