use CURLSSLBACKEND_NONE #11909
Closed
use CURLSSLBACKEND_NONE #11909
Conversation
This file contains 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
[ssl] use CURLSSLBACKEND_NONE instead of (curl_sslbackend)-1 in documentation and examples. Signed-off-by: Ted Lyngmo <ted@lyncon.se>
bagder
approved these changes
Sep 21, 2023
|
Thanks! |
|
|
This is just a side-effect of GitHub not offering any way to signal that it was merged manually. Maybe in a future we get a |
ptitSeb
pushed a commit
to wasix-org/curl
that referenced
this pull request
Sep 25, 2023
[ssl] use CURLSSLBACKEND_NONE instead of (curl_sslbackend)-1 in documentation and examples. Signed-off-by: Ted Lyngmo <ted@lyncon.se> Closes curl#11909
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.
[ssl] use CURLSSLBACKEND_NONE instead of (curl_sslbackend)-1 in documentation and examples.