Fix #2360 by reverting "set GIT_SSL_NO_VERIFY for opposite value than#2361
Merged
Conversation
… than strictSsl" This reverts commit f0a54d0.
Contributor
Author
|
Please see #2360 for details. Travis was green in my fork. Everything should be green here too. I hope this gets merged sometime soon :) |
Contributor
|
thank you! |
This was referenced Apr 24, 2020
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
2 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 #2360 by reverting "set GIT_SSL_NO_VERIFY for opposite value than strictSsl"
This reverts commit f0a54d0 and adds some comments in the tests