Re: git and larger trees, not so fast?

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 10, 2007, 03:48 UTC
Message-ID: <7v643ovyli.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <alpine.LFD.0.999.0708091754150.25146@woody.linux-foundation.org>

Linus Torvalds <torvalds@linux-foundation.org> writes:

> (I didn't test it, though, maybe I missed something).

I do not think the change affects the normal codepath. The one-liner patch to git-commit.sh touches the codepath that updates the index used only to write out the partial commit, and losing the cached stat info from that index does not matter, as that index is removed immediately after writing the tree out and is never compared with working tree as far as I can tell.

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