Skip to content

Conversation

@lhchavez
Copy link
Contributor

@lhchavez lhchavez commented Sep 5, 2021

We can't yet ship a fully libgit2 v1.2.0-compatible library due to a
missing public symbol, but we can allow the v1.1.0-era codebase to link
against libgit2 v1.2.0 in the meantime.

@lhchavez lhchavez force-pushed the forwards-compat-v1.2.0 branch 2 times, most recently from 2bcd478 to f825eb3 Compare September 5, 2021 03:01
We can't yet ship a fully libgit2 v1.2.0-compatible library due to a
missing public symbol, but we can allow the v1.1.0-era codebase to link
against libgit2 v1.2.0 in the meantime.
@lhchavez lhchavez force-pushed the forwards-compat-v1.2.0 branch from f825eb3 to 7299adf Compare September 5, 2021 03:05
@lhchavez lhchavez merged commit 549706b into libgit2:main Sep 5, 2021
@lhchavez lhchavez deleted the forwards-compat-v1.2.0 branch September 5, 2021 03:07
lhchavez added a commit that referenced this pull request Sep 5, 2021
We can't yet ship a fully libgit2 v1.2.0-compatible library due to a
missing public symbol, but we can allow the v1.1.0-era codebase to link
against libgit2 v1.2.0 in the meantime.

(cherry picked from commit 549706b)
lhchavez added a commit that referenced this pull request Sep 5, 2021
We can't yet ship a fully libgit2 v1.2.0-compatible library due to a
missing public symbol, but we can allow the v1.1.0-era codebase to link
against libgit2 v1.2.0 in the meantime.

(cherry picked from commit 549706b)
lhchavez added a commit to lhchavez/git2go that referenced this pull request Oct 16, 2021
This commit marks this (Golang) version of git2go as being compatible
with libgit2 v1.3.0.
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.

1 participant