Upgrade git2 to v0.17.1 #57
Merged
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
Signed-off-by: Demetrious Robinson <[email protected]>
Signed-off-by: Demetrious Robinson <[email protected]>
…s initials directly
This reverts commit fbbe69f.
This reverts commit dc04ea6.
|
Thanks for the work! |
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.
Upgrading git2 to v0.17.1 seems to resolve the M1 libssl issues reported by users in issues such as #52
This has a deceptively long commit history given that I was originally using my fork to add new functionality on top of what this tool does. However, I've isolated that work into a branch and only retained the changes the fix the existing behavior of this tool for M1 chips.