summaryrefslogtreecommitdiff
path: root/block-sha1/sha1.c
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2018-04-06 14:58:32 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-04-09 06:14:45 +0900
commit53df97a29d78070f3dfaf3e4d9a5ae61f33d7906 (patch)
tree98aa44a9d000da1f66fd8ff7c9eabc9377d1ec9d /block-sha1/sha1.c
parentGit 2.17 (diff)
downloadtgif-53df97a29d78070f3dfaf3e4d9a5ae61f33d7906.tar.xz
ref-filter: use "struct object_id" consistently
Internally we store a "struct object_id", and all of our callers have one to pass us. But we insist that they peel it to its bare-sha1 hash, which we then hashcpy() into place. Let's pass it around as an object_id, which future-proofs us for a post-sha1 world. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'block-sha1/sha1.c')
0 files changed, 0 insertions, 0 deletions