• https://github.com/libgit2/libgit2/archive/v1.4.3/ (Download)

• (2022-04-13) Updated to version: libgit2-1.4.3
• (2022-02-27) Updated to version: libgit2-1.4.2
• (2022-02-19) Updated to version: libgit2-1.4.1
• (2022-02-15) Updated to version: libgit2-1.4.0
• (2021-11-19) Updated to version: libgit2-1.3.0
• (2021-08-31) Updated to version: libgit2-1.1.1
• (2020-11-07) Updated to version: libgit2-1.1.0
• (2019-12-30) Updated to version: libgit2-0.28.4
• (2019-11-09) Updated to version: libgit2-0.28.2
• (2019-05-04) Updated to version: libgit2-0.28.1

Log message:
Update to libgit2-1.3.0.

Log message:
Reverse the polarity of MODPY_VERSION; default is now 3.x,
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.

Log message:
update libgit2 to 1.1.0

Log message:
Build/test with Python 3
Required at build for detection but used only for testing;  works fine
on a system without Python 2.  If 2 and 3 are installed, 3 is preferred.

Log message:
- update to libgit2-0.28.4 which contains a number of security fixes.
judging by the changelog we're only affected by issues addressed in 0.28.3

Log message:
Update to libgit2-0.28.2.

Log message:
update to libgit2-0.28.1

Log message:
update to libgit2-0.27.8

Log message:
Security update to libgit2-0.27.7
CVE-2018-17456 (<0.27.5)
CVE-2018-10887 (<0.27.3)
CVE-2018-10888 (<0.27.3)
From Hiltjo Posthuma, thanks!

Log message:
update to libgit2-0.27.2

Log message:
update to libgit2-0.27.1, addressing CVE-2018-11235

Log message:
update to libgit2-0.27.0

Log message:
update to libgit2-0.26.3, includes security fixes as part of 0.26.2:
"memory handling issues when reading crafted repository index files.
The issues allow for possible denial of service due to allocation of large
memory and out-of-bound reads. As the index is never transferred via the
network, exploitation requires an attacker to have access to the local repository."

Log message:
unbreak, now libressl has all the functions this needs

Log message:
unbreak again; we now have all the BIO_* that libgit2 uses apart from BIO_get_new_index()

Log message:
fix now that libressl has some new BIO_*, from jsing

Log message:
add "defined(LIBRESSL_VERSION_NUMBER) && " to the ifdef

Log message:
adapt compat code conditionals for ASN1_STRING_get0_data() to unbreak
since it was added in libressl, ok jsing

Log message:
Now that arm has switched to clang the base compiler has atomic builtins
and accepts -mfpu=neon.
ok jca@ sthen@

Log message:
Update to libgit2-0.26.0.

Log message:
missing patch from upstream to unbreak with libressl; no bump as it wouldn't build

Log message:
update to libgit2-0.25.1

Log message:
use ports gcc on arm to get atomic builtins

Log message:
update libgit2 and py-git2 to 0.24.1
Make better use of GH_* and python MODULE.
OK shadchin@

Log message:
update to libgit2-0.24.0

Log message:
Don't attempt to build on arm.  sync atomic builtins required.

Log message:
mark broken on sparc, requires atomic ops

Log message:
Remove more BROKEN markers for ports requiring built-in atomic ops.
from Brad, OK jasper@

Log message:
update to libgit2-0.23.3

Log message:
broken on mips64, no atomic ops

Log message:
update to libgit2-0.22.2

Log message:
BROKEN-hppa =  no atomic ops

Log message:
Update to libgit2-0.22.1.
with and ok jasper@

Log message:
update to libgit2-0.21.3