delta/libgit2.git/src/libgit2/odb.c, branch ethomson/objectformat github.com: libgit2/libgit2.git sha256: indirection for experimental functions 2022-07-14T02:50:33+00:00 Edward Thomson ethomson@edwardthomson.com 2022-07-14T02:25:11+00:00 b43567d655b6fbc562a165095a6980d19c4ae278 The experimental function signature is only available when `GIT_EXPERIMENTAL_SHA256` is enabled. 
The experimental function signature is only available when
`GIT_EXPERIMENTAL_SHA256` is enabled.
sha256: make sha256 an experimental optional feature 2022-06-20T21:12:49+00:00 Edward Thomson ethomson@edwardthomson.com 2022-06-15T02:29:10+00:00 6c57bac6b18f6a30e1a8c8272a8dc367f202aa88 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. 
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.
odb_loose: SHA256 support for loose object storage 2022-06-20T21:09:47+00:00 Edward Thomson ethomson@edwardthomson.com 2022-01-26T18:10:01+00:00 04f34688c43d28d1fa110df7d32e8665232199ff Teach the loose object database how to cope with SHA256 objects. 
Teach the loose object database how to cope with SHA256 objects.
odb: add git_odb_loose_backend_options 2022-06-20T21:09:47+00:00 Edward Thomson ethomson@edwardthomson.com 2021-12-12T14:19:25+00:00 4d7ec76c42d9bcf2ed4f59e0efff2f4e6e810808 Move the arguments to `git_odb_loose` into an options structure. 
Move the arguments to `git_odb_loose` into an options structure.
odb: accept an oid type in options 2022-06-20T21:09:46+00:00 Edward Thomson ethomson@edwardthomson.com 2022-01-26T18:57:48+00:00 dbccfc203e776196ea2901dbcb652bba6a848a30 Allow the object database to take an oid type that it supports. This oid type will be used to validate the objects that the backends provide. 
Allow the object database to take an oid type that it supports.  This
oid type will be used to validate the objects that the backends provide.
odb: add git_odb_options 2022-06-20T21:05:30+00:00 Edward Thomson ethomson@edwardthomson.com 2022-01-26T18:02:49+00:00 3eba9181cf74693d5906c799e08aba15b5745355 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. 
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.
odb_hash*: accept the oid type to hash into 2022-06-20T21:05:29+00:00 Edward Thomson ethomson@edwardthomson.com 2022-01-26T18:07:28+00:00 8444b6dce71d53a44f300d7c023cdd075faaa872 The git_odb_hash helper functions should not assume SHA1, and instead should be given the oid type that they're producing. 
The git_odb_hash helper functions should not assume SHA1, and instead
should be given the oid type that they're producing.
oid: give oids a type 2022-06-20T21:05:29+00:00 Edward Thomson ethomson@edwardthomson.com 2022-01-23T14:47:01+00:00 3fbf580c91935ccdea25a135204419991f503b63 `git_oid`s now have a type, and we require the oid type when creating the object id from creation functions. 
`git_oid`s now have a type, and we require the oid type when creating
the object id from creation functions.
oid: define GIT_OID_SHA1_ZERO 2022-06-15T02:29:57+00:00 Edward Thomson ethomson@edwardthomson.com 2022-01-17T18:40:37+00:00 0acaf3a8eb7c3276b7864df8f5588c7007b38f35 Callers should not assume the layout of the oid structure; provide them a macro that defines the null / zero sha1 object id. 
Callers should not assume the layout of the oid structure; provide them
a macro that defines the null / zero sha1 object id.
oid: `GIT_OID_*SZ` is now `GIT_OID_SHA1_*SIZE` 2022-06-15T02:29:57+00:00 Edward Thomson ethomson@edwardthomson.com 2022-01-23T04:10:03+00:00 dbc4ac1c76827e954e0aa27afe8bb7e0b8993a93 In preparation for SHA256 support, `GIT_OID_RAWSZ` and `GIT_OID_HEXSZ` need to indicate that they're the size of _SHA1_ OIDs. 
In preparation for SHA256 support, `GIT_OID_RAWSZ` and `GIT_OID_HEXSZ`
need to indicate that they're the size of _SHA1_ OIDs.