summaryrefslogtreecommitdiff
path: root/builtin/verify-tag.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2018-04-06 14:58:32 -0400
committerJunio C Hamano <gitster@pobox.com>2018-04-09 06:14:45 +0900
commit53df97a29d78070f3dfaf3e4d9a5ae61f33d7906 (patch)
tree98aa44a9d000da1f66fd8ff7c9eabc9377d1ec9d /builtin/verify-tag.c
parent468165c1d8a442994a825f3684528361727cd8c0 (diff)
downloadgit-53df97a29d78070f3dfaf3e4d9a5ae61f33d7906.tar.gz
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 'builtin/verify-tag.c')
-rw-r--r--builtin/verify-tag.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/builtin/verify-tag.c b/builtin/verify-tag.c
index ad7b79fa5c..6fa04b751a 100644
--- a/builtin/verify-tag.c
+++ b/builtin/verify-tag.c
@@ -72,7 +72,7 @@ int cmd_verify_tag(int argc, const char **argv, const char *prefix)
}
if (format.format)
- pretty_print_ref(name, oid.hash, &format);
+ pretty_print_ref(name, &oid, &format);
}
return had_error;
}