Re: [PATCH v4 2/4] sparse-index: avoid unnecessary cache tree clearing

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 29, 2021, 20:01 UTC
Message-ID: <xmqq7ddvlhwn.fsf@gitster.g>
In-Reply-To: <006b1747-fc6b-61e4-7ce9-f0a6687ddd8f@gmail.com>

Derrick Stolee <stolee@gmail.com> writes:

Show 5 quoted lines

> I think in this pruned form, the cache-tree is valid and serves all of
> the roles it was designed for. We can quickly compute the root tree in
> 'git commit'. We can navigate the cache-tree in traverse_by_cache_tree()
> to accurately describe the trees in the index. These things are tested
> in t1092 and the p2000 performance test.

OK, then I was worried too much.  Thanks for clarifying.

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