- 10 Dec, 2019 1 commit
-
-
Patrick Steinhardt committed
-
- 04 Dec, 2019 2 commits
-
-
I encountered some problematic URLs, and was delighted to see that they were already fixed. I figured I may as well add them to the changelog. For the record, URLs with no path used to be rejected. That is arguably correct, but command line git accepts them. URLs with a path of / and a non-standard port used to have their port completely ignored!
Josh Bleecher Snyder committed -
Note that for security releases, we update the two most recent major release branches.
Edward Thomson committed
-
- 13 Sep, 2019 1 commit
-
-
Etienne Samson committed
-
- 13 Aug, 2019 1 commit
-
-
Edward Thomson committed
-
- 14 Jun, 2019 1 commit
-
-
The interactions between `USE_HTTPS` and `SHA1_BACKEND` have been streamlined. Previously we would have accepted not quite working configurations (like, `-DUSE_HTTPS=OFF -DSHA1_BACKEND=OpenSSL`) and, as the OpenSSL detection only ran with `USE_HTTPS`, the link would fail. The detection was moved to a new `USE_SHA1`, modeled after `USE_HTTPS`, which takes the values "CollisionDetection/Backend/Generic", to better match how the "hashing backend" is selected, the default (ON) being "CollisionDetection". Note that, as `SHA1_BACKEND` is still used internally, you might need to check what customization you're using it for.
Etienne Samson committed
-
- 13 Jun, 2019 1 commit
-
-
Our bundled http-parser includes bugfixes, therefore we should prefer our http-parser until such time as we can identify that the system http-parser has these bugfixes (using a version check). Since these bugs are - at present - minor, retain the ability for users to force that they want to use the system http-parser anyway. This does change the cmake specification so that people _must_ opt-in to the new behavior knowingly.
Edward Thomson committed
-
- 27 Feb, 2019 2 commits
-
-
Edward Thomson committed
-
Edward Thomson committed
-
- 07 Feb, 2019 1 commit
-
-
Etienne Samson committed
-
- 31 Jan, 2019 1 commit
-
-
Edward Thomson committed
-
- 28 Jan, 2019 1 commit
-
-
Etienne Samson committed
-
- 25 Jan, 2019 1 commit
-
-
Edward Thomson committed
-
- 24 Jan, 2019 1 commit
-
-
Previously, we would clobber any extension-specific error message with an "extension is truncated" message. This makes `read_extension` correctly preserve those errors, takes responsibility for truncation errors, and adds a new message with the actual extension signature for unsupported mandatory extensions.
Etienne Samson committed
-
- 22 Jan, 2019 1 commit
-
-
Edward Thomson committed
-
- 17 Jan, 2019 6 commits
-
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
Edward Thomson committed
-
- 19 Oct, 2018 1 commit
-
-
Carlos Martín Nieto committed
-
- 30 Aug, 2018 1 commit
-
-
While our contribution guide tries to make clear the licenses that apply to libgit2, it does not make clear that different licenses apply to our bundled dependencies. Make this clear by listing each dependency together with the licenses that they are governed by. Furthermore, bundle the complete license texts next to the code they apply to.
Patrick Steinhardt committed
-
- 27 Aug, 2018 1 commit
-
-
Johan Abildskov committed
-
- 20 Aug, 2018 2 commits
-
-
Johan Abildskov committed
-
Johan Abildskov committed
-
- 03 Aug, 2018 3 commits
-
-
Both the USE_SANITIZER and USE_COVERAGE options are convenience options that turn on a set of CFLAGS. Despite our own set of CFLAGS required to build libgit2, we have no real business to mess with them, though, as they can easily be passed in by the user via specifying the CFLAGS environment variable. The reasoning behind not providing them is that as soon as we start adding those for some usecases, users might ask for other sets of CFLAGS catering to their specific need in another usecase. Thus, we do not want to support them here.
Patrick Steinhardt committed -
Right now, users are being instrucded to add the "-DCMAKE_EXE_LINKER_FLAGS=-fsanitize=fuzzer" flag when they want to build our fuzzers. This is error-prone and user unfriendly. Instead, just add the flag to our fuzzers' build instructions so that it happens automatically. Adjust the README accordingly.
Patrick Steinhardt committed -
Patrick Steinhardt committed
-
- 29 Jun, 2018 1 commit
-
-
Edward Thomson committed
-
- 12 Jun, 2018 1 commit
-
-
The libgit2 project mostly follows the coding style of git and thus the linux project. While those two projects use a recommended tab width of eight spaces, we instruct users to set their editor's tab width to four spaces. Fix this to say eight instead.
Patrick Steinhardt committed
-
- 09 Jun, 2018 1 commit
-
-
We've introduced a manifest for the clib version system that includes a version number; we should update it at release time to correspond with the version number in the header.
Edward Thomson committed
-
- 30 May, 2018 1 commit
-
-
Our non-technical documents are currently floating around loosely in our project's root, making it harden than necessary to discover what one is searching for. We do have a "docs/" directory, though, which serves exactly that purpose of hosting documentation. Move our non-technical documentation into the "docs/" directory. Adjust all links to these documents.
Patrick Steinhardt committed
-
- 21 May, 2018 1 commit
-
-
Jason Haslam committed
-
- 02 May, 2018 1 commit
-
-
Carson Howard committed
-
- 30 Mar, 2018 1 commit
-
-
Carson Howard committed
-
- 20 Feb, 2018 1 commit
-
-
Patrick Steinhardt committed
-
- 15 Feb, 2018 1 commit
-
-
Patrick Steinhardt committed
-
- 27 Jan, 2018 1 commit
-
-
Carlos Martín Nieto committed
-
- 19 Jan, 2018 1 commit
-
-
This should provide the release manager enough to know which steps to take when it's time to cut a new release.
Carlos Martín Nieto committed
-