Re: [PATCH v3 1/3] packed-backend: fsck should allow an empty "packed-refs" file

From: Junio C Hamano <gitster@pobox.com>
Date: May 12, 2025, 17:18 UTC
Message-ID: <xmqqh61pu4r9.fsf@gitster.g>
In-Reply-To: <20250512155654.GA1219668@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 9 quoted lines

> It may be useful for fsck to detect this, though, even if the default
> message severity is set to "info" or even "ignore. That would allow
> people who know they are using modern Git to increase it themselves (I
> don't expect normal users to do this, but it would probably be useful
> for forges which run automated "fsck" across a lot of repos).
>
> And then the backwards-incompatible Git 3.0 thing would just be tweaking
> the severity of the config (and in the meantime, it would help flush out
> any unexpected instances people run into).

I came to make a same comment but the above has everything I wanted to say (and more).

$ 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.