Re: [PATCH v2 08/10] sparse-index: complete partial expansion
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 25, 2022, 16:32 UTC
- Message-ID
- <xmqq35gxa7zc.fsf@gitster.g>
- In-Reply-To
- <f0327fd6-f2b3-64b6-3a34-2a7bbad20a01@github.com>
Derrick Stolee <derrickstolee@github.com> writes:
Show 7 quoted lines
> If a user is in a conflict state and modifies their sparse-checkout > cone, then we will hit this "recompute the cache-tree" state, fail, > and cause full index expansion. I think that combination (have a > conflict AND modify sparse-checkout cone) is rare enough to not > optimize for (yet). > > Does that make the situation more clear?
Yes. "AND modify sparse-checkout cone" part was what I was missing. I didn't see it because it wasn't there at all in the code that was removed or added---it comes from the fact that the user is running the "sparse-checkout" command in the first place, and that was what I missed.
Thanks.