Re: [PATCH 16/18] fsck: support demoting errors to warnings

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 23, 2014, 17:07 UTC
Message-ID: <xmqqegrq47n1.fsf@gitster.dls.corp.google.com>
In-Reply-To: <xmqqmw6e499u.fsf@gitster.dls.corp.google.com>

Junio C Hamano <gitster@pobox.com> writes:

> I suspect that it would be much better if the configuration
> variables were organized the other way around, e.g.
>
> 	$ git config fsck.warn missingTagger,someOtherKindOfError

By the way, I think I like this organization is much better than the other way around, i.e. "fsck.missingTagger=warn", as we do not want the namespace under fsck.* for variables that control the behaviour of fsck that are *NOT* kinds of questionable conditions fsck can find.

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