Skip to content

Conversation

tiennou
Copy link
Contributor

@tiennou tiennou commented Jun 19, 2017

Now that 0.26 is a thing.

Tests have been run locally.

@pietbrauer
Copy link
Member

Seems that Travis can't checkout one of the libgit2 example repositories?

@tiennou
Copy link
Contributor Author

tiennou commented Jun 19, 2017

Yep, they have a deliberately broken submodule file that --recursive tries to update.

libgit2/libgit2#4274

@tiennou tiennou force-pushed the update-libgit2-0.26 branch from b35c555 to 1043a54 Compare July 17, 2017 13:43
@tiennou
Copy link
Contributor Author

tiennou commented Jul 17, 2017

I've repointed the submodule to my fixed branch (which is maint/0.26 + the submodule delete) so this should be good as a first approximation.

@pietbrauer
Copy link
Member

pietbrauer commented Jul 19, 2017

I personally wouldn't like a "personal" fork of libgit2 for the submodule. We should wait for the issue to be fixed on their side.

@slavikus
Copy link
Contributor

Looks like libgit2 got this fixed, can we get back to this one, guys?

@pietbrauer
Copy link
Member

I’m all for it.

Really, sometimes after 0.26, because of a test .gitmodules which would make Travis fail.
@tiennou tiennou force-pushed the update-libgit2-0.26 branch from 1043a54 to e605d96 Compare November 26, 2017 12:05
@tiennou
Copy link
Contributor Author

tiennou commented Nov 26, 2017

Updated !

@pietbrauer
Copy link
Member

Sweet!

@pietbrauer pietbrauer merged commit ee84447 into libgit2:master Nov 26, 2017
@tiennou tiennou deleted the update-libgit2-0.26 branch November 26, 2017 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants