crypto: move node_crypto_clienthello-inl.h to cc#17606
Closed
danbev wants to merge 1 commit intonodejs:masterfrom
Closed
crypto: move node_crypto_clienthello-inl.h to cc#17606danbev wants to merge 1 commit intonodejs:masterfrom
danbev wants to merge 1 commit intonodejs:masterfrom
Conversation
This commit updates node_crypto.h to just include node_crypto_clienthello.h instead of the inline header. Also node_crypto.cc is updated to include node_crypto_clienthello-inl.h.
Contributor
Author
bnoordhuis
approved these changes
Dec 11, 2017
Member
|
Should this be fast tracked? |
Member
|
Should still be fast tracked? |
jasnell
approved these changes
Dec 12, 2017
Contributor
Author
|
Landed in 47edfd9 |
danbev
added a commit
that referenced
this pull request
Dec 13, 2017
This commit updates node_crypto.h to just include node_crypto_clienthello.h instead of the inline header. Also node_crypto.cc is updated to include node_crypto_clienthello-inl.h. PR-URL: #17606 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
MylesBorins
pushed a commit
that referenced
this pull request
Jan 8, 2018
This commit updates node_crypto.h to just include node_crypto_clienthello.h instead of the inline header. Also node_crypto.cc is updated to include node_crypto_clienthello-inl.h. PR-URL: #17606 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
Merged
Contributor
|
Does this make sense for LTS? It does not land cleanly on v6.x and creates new compiler warnings for v8.x |
Contributor
|
ping re: backport |
Contributor
Author
|
@MylesBorins Sorry about the delay, I'll take a look at backporting today. |
Contributor
Author
|
@MylesBorins I don't think this is worth backporting to v6.x as it will require multiple changes to other files in addition to the ones in this pull request. I'll take a look at the warning backporting to v8.x now. |
Contributor
Author
|
I've taken a look and the same warnings are generated for 8.x as for 6.x. I don't think this is worth back porting. Let me know if you feel differently. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit updates
node_crypto.hto just includenode_crypto_clienthello.hinstead of the inline header. Alsonode_crypto.ccis updated to includenode_crypto_clienthello-inl.h.Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passescrypto
Affected core subsystem(s)