Re: [PATCH v3 6/8] reset: make sparse-aware (except --mixed)

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 11, 2021, 16:16 UTC
Message-ID: <xmqqh7dnczb3.fsf@gitster.g>
In-Reply-To: <4a002488-09ba-efed-ac70-c0ec16d7dbe2@github.com>

Victoria Dye <vdye@github.com> writes:

Show 7 quoted lines

> After some basic performance testing of `git reset [--hard]`, it's not clear
> whether `cache_tree_update` is definitively faster or slower than
> `prime_cache_tree`; more conclusive results would indicate which of the two
> could be skipped. I'd like to defer this to a future patch (tracking it with
> an internal issue so I don't forget) where I can perform a more thorough
> analysis across all of the commands currently using `prime_cache_tree` and
> update its usage accordingly.

Yup. That sounds sensible. Concentrating on correctness first is a good direction to go.

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