Johan Herland [off-list ref] writes:
quoted
This won't practically be problem in newer repositories, but it
is somewhat annoying. Perhaps do this only under the new -v
option to git-fsck, say "warning" not "error", and not exit with
non-zero because of this?
Like this?
Or would you rather switch around the "verbose" and the
"parse_and_verify_tag_buffer()" (i.e. not even attempt the thorough
verification unless in verbose mode)?
Actually I was thinking about doing something like this.
- if (parse_and_verify_tag_buffer(0, data, size, 1) && verbose)
+ if (parse_and_verify_tag_buffer(0, data, size, verbose))