Re: [PATCH v3 17/17] fsck: report invalid object type-path combinations

From: Jonathan Tan <jonathantanmy@google.com>
Date: May 27, 2021, 18:28 UTC
Message-ID: <20210527182811.2682205-1-jonathantanmy@google.com>
In-Reply-To: <patch-17.17-c5e6686765-20210520T111610Z-avarab@gmail.com>

> Improve the error that's emitted in cases where we find a loose object
> we parse, but which isn't at the location we expect it to be.

I'll hold off reviewing this for 2 reasons - firstly, I don't think it's related to the other patches that are about reporting a wrong object type, and secondly, in the case of repository corruption, I don't see how useful computing (and reporting) the hash of a corrupt object is.

If someone else wants to take a look at this, that would be great, but otherwise I would suggest splitting this into its own patch set.

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