Re: [PATCH] Teach "git add" and friends to be paranoid

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 19, 2010, 17:51 UTC
Message-ID: <7vbpflktaf.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20100218153249.GA11733@gibbs.hungrycats.org>

Zygo Blaxell <zblaxell@gibbs.hungrycats.org> writes:

> If git commit runs out of disk space, for example, the commit should
> fail, but the repository should still not be corrupt.  Future commits
> (for example after freeing some disk space) should eventually succeed.

That is true. It is Ok to create a corrupt object as long as running an equivalent of fsck immediately after an object creation to catch the breakage to prevent it from propagating further.

That is essentially what "paranoid" switch does, but it adds overhead that is unnecessary for the use case we primarily target in git.

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