Upgrade libgit2 to 1.3.1#1894
Conversation
11ec270 to
45b815c
Compare
0f65006 to
42faeed
Compare
42faeed to
9e1649b
Compare
ianhattendorf
left a comment
There was a problem hiding this comment.
Looking good, just a few things to address.
AlexaXs
left a comment
There was a problem hiding this comment.
Changes in vendor/libgit2 look good. Merged changes onto libgit2-1.3.0 maintain the original code semantics.
0acfe03 to
f7d63bb
Compare
00daf09 to
8b41a6a
Compare
|
In the meantime libgit 1.4.2 is out, would that be an easy upgrade? |
|
@wmertens when I started this 1.4 had just come out and we decided to make changes incrememental rather than large(r) version jumps to help with API stabilization and minimize implementation problems. I do have the 1.4 upgrade in my backlog but I think theres some higher priority tasks to get done first(at least from my end) like filter streaming. The actual upgrade to 1.4 doesn't look super complex but i wouldn't no for certain until I start working on it. |
|
In light of the recent libgit2 security release, I'll update this PR to use libgit 1.3.1. Luckily this won't require any code or libgit2-docs changes. I've already confirmed it builds. @ianhattendorf I've updated my fork of the libgit-next branch. Please push it when convenient and I'll update the submodule in this PR. https://github.com/zawata/libgit2/tree/libgit-next |
|
PR updated to libgit2 v1.3.1 |
df309c1 to
8a48d37
Compare
5ba1a66 to
4ecc785
Compare
1de439f to
4ecc785
Compare
Several changes were made:
Note: A majority of the PR changes are the new Libgit2-docs.json