Re: [PATCH 3/6] git-fsck: Do thorough verification of tag objects.

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 6, 2007, 07:18 UTC
Message-ID: <7vtztl7dqi.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <200706040951.06620.johan@herland.net>

Johan Herland <johan@herland.net> writes:

> Teach git-fsck to do the same kind of verification on tag objects that is
> already done by git-mktag.

The tagger field was introduced mid July 2005; any repository with a tag object older than that would now get non-zero exit from fsck.

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?

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.