Re: [PATCH 00/18] Introduce an internal API to interact with the fsck machinery

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 10, 2014, 18:34 UTC
Message-ID: <xmqqr3w7gxr4.fsf@gitster.dls.corp.google.com>
In-Reply-To: <cover.1418055173.git.johannes.schindelin@gmx.de>

Johannes Schindelin <johannes.schindelin@gmx.de> writes:

Show 8 quoted lines

> At the moment, the git-fsck's integrity checks are targeted toward the
> end user, i.e. the error messages are really just messages, intended for
> human consumption.
>
> Under certain circumstances, some of those errors should be allowed to
> be turned into mere warnings, though, because the cost of fixing the
> issues might well be larger than the cost of carrying those flawed
> objects.

Overall I very much like what this series aims to do. Thanks for working on 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.