Bump libgit2 to 1.7.2 #1990
Merged
Bump libgit2 to 1.7.2 #1990
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
zawata
force-pushed
the
bump/libgit2-1.7.2
branch
from
375e709
to
b8334d2
Compare
this has been upstreamed
this is now missing from the auto-generated libgit2 documentation because the function declaration is behind a preprocessor check
the OID of the resulting commit has changed because the conflicts list of a Merge conflict is no longer commented, thus changing the commit message. the other content of the commit is unchanged
nothing changed about this function but for some reason, the last message in the reflog is now a clone message, instead of the reflog we expect.
zawata
force-pushed
the
bump/libgit2-1.7.2
branch
from
f065aef
to
4027c95
Compare
ianhattendorf
approved these changes
Feb 14, 2024
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.
Bumps libgit2 to 1.7.2 to address security vulnerabilities.
Updates for 1.3.1 to 1.5.0 are documented in my last PR: #1929.
libgit2 commit still needs to be pushed to
nodegit/libgit2, I don't have access to it.