- 12 Feb, 2023 3 commits
-
-
Edward Thomson committed
-
Teach the packfile machinery to cope with SHA256.
Edward Thomson committed -
In clar, an underscore is meaningful; avoid using it incorrectly / unnecessarily.
Edward Thomson committed
-
- 19 Sep, 2022 1 commit
-
-
Actually `cl_skip` the sha256 tests when we're not compiled for sha256, instead of passing them.
Edward Thomson committed
-
- 14 Jul, 2022 1 commit
-
-
The experimental function signature is only available when `GIT_EXPERIMENTAL_SHA256` is enabled.
Edward Thomson committed
-
- 20 Jun, 2022 5 commits
-
-
libgit2 can be built with optional, experimental sha256 support. This allows consumers to begin testing and providing feedback for our sha256 support while we continue to develop it, and allows us to make API breaking changes while we iterate on a final sha256 implementation. The results will be `git2-experimental.dll` and installed as `git2-experimental.h` to avoid confusion with a production libgit2.
Edward Thomson committed -
Teach the loose object database how to cope with SHA256 objects.
Edward Thomson committed -
Move the arguments to `git_odb_loose` into an options structure.
Edward Thomson committed -
Users will need to be able to specify the object id type for the given object database; add a new `git_odb_options` with that option.
Edward Thomson committed -
`git_oid`s now have a type, and we require the oid type when creating the object id from creation functions.
Edward Thomson committed
-
- 15 Jun, 2022 2 commits
-
-
Callers should not assume the layout of the oid structure; provide them a macro that defines the null / zero sha1 object id.
Edward Thomson committed -
In preparation for SHA256 support, `GIT_OID_RAWSZ` and `GIT_OID_HEXSZ` need to indicate that they're the size of _SHA1_ OIDs.
Edward Thomson committed
-
- 23 Feb, 2022 1 commit
-
-
Like we want to separate libgit2 and utility source code, we want to separate libgit2 and utility tests. Start by moving all the tests into libgit2.
Edward Thomson committed
-