diff options
author | Ævar Arnfjörð Bjarmason <avarab@gmail.com> | 2022-01-27 06:26:45 +0100 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2022-01-27 12:09:33 -0800 |
commit | 667a560be7ae977e61d81ca4bcb95ded1cdacc9c (patch) | |
tree | f95e7fac76a0a526c8f612dfb343bfc05bfdcb89 /object.c | |
parent | object-name: explicitly handle OBJ_BAD in show_ambiguous_object() (diff) | |
download | tgif-667a560be7ae977e61d81ca4bcb95ded1cdacc9c.tar.xz |
object-name: explicitly handle bad tags in show_ambiguous_object()
Follow-up the handling of OBJ_BAD in the preceding commit and
explicitly handle those cases where parse_tag() fails, or we don't end
up with a non-NULL pointer in in tag->tag.
If we run into such a tag we'd previously be silent about it. We
really should also be handling these batter in parse_tag_buffer() by
being more eager to emit an error(), instead of silently aborting with
"return -1;".
One example of such a tag is the one that's tested for in
"t3800-mktag.sh", where the code takes the "size <
the_hash_algo->hexsz + 24" branch.
But in lieu of earlier missing "error" output let's show the user
something to indicate why we're not showing a tag message in these
cases, now instead of showing:
hint: deadbeef tag
We'll instead display:
hint: deadbeef tag [tag could not be parsed]
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'object.c')
0 files changed, 0 insertions, 0 deletions