diff options
| author |  brian m. carlson <sandals@crustytoothpaste.net> | 2021-04-26 01:03:00 +0000 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2021-04-27 16:31:39 +0900 |
| commit | b8505ecbf2b1e4ef27b9597fd113cb1679792b29 (patch) | |
| tree | 4394a10a7d4c08e781ff062fd876e876fda48d0e /t/t5515/fetch.br-branches-one_branches-one | |
| parent | builtin/pack-objects: avoid using struct object_id for pack hash (diff) | |
| download | tgif-b8505ecbf2b1e4ef27b9597fd113cb1679792b29.tar.xz | |
hex: default to the_hash_algo on zero algorithm value
There are numerous places in the codebase where we assume we can
initialize data by zeroing all its bytes. However, when we do that with
a struct object_id, it leaves the structure with a zero value for the
algorithm, which is invalid.
We could forbid this pattern and require that all struct object_id
instances be initialized using oidclr, but this seems burdensome and
it's unnatural to most C programmers. Instead, if the algorithm is
zero, assume we wanted to use the default hash algorithm instead.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/fetch.br-branches-one_branches-one')
0 files changed, 0 insertions, 0 deletions