git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/3] Fix use of 'cache_bottom' in sparse index

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 16, 2022, 20:21 UTC
Message-ID
<xmqq5yodlkc9.fsf@gitster.g>
In-Reply-To
<pull.1179.git.1647461522.gitgitgadget@gmail.com>
"Victoria Dye via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 7 quoted lines
> ...
> To fix this, the 'cache_bottom' advancement is reinstated in
> 'mark_ce_used(...)', and instead it is disabled in 'unpack_callback(...)' if
> the tree in question is a sparse directory. This corrects both the
> non-"cache diff" cases and the 'unpack_index_entry(...)' cases while
> preventing the double-advancement 17a1bb570b originally intended to avoid
> (patch [2/3]).
;-).
Previous: Victoria Dye via GitGitGadgetNext: Victoria Dye via GitGitGadget
Message 5 of 12 in “Fix use of 'cache_bottom' in sparse index”
  1. 0/3 Fix use of 'cache_bottom' in sparse indexVictoria Dye via GitGitGadget, Mar 16, 2022
  2. 1/3 t1092: add sparse directory before cone in test repoVictoria Dye via GitGitGadget, Mar 16, 2022
  3. 2/3 unpack-trees: increment cache_bottom for sparse directoriesVictoria Dye via GitGitGadget, Mar 16, 2022
  4. 3/3 Revert "unpack-trees: improve performance of next_cache_entry"Victoria Dye via GitGitGadget, Mar 16, 2022
  5. Junio C HamanoMar 16, 2022
  6. 0/3 Fix use of 'cache_bottom' in sparse indexVictoria Dye via GitGitGadget, Mar 17, 2022
  7. 1/3 t1092: add sparse directory before cone in test repoVictoria Dye via GitGitGadget, Mar 17, 2022
  8. 2/3 unpack-trees: increment cache_bottom for sparse directoriesVictoria Dye via GitGitGadget, Mar 17, 2022
  9. Derrick StoleeMar 21, 2022
  10. Junio C HamanoMar 21, 2022
  11. 3/3 Revert "unpack-trees: improve performance of next_cache_entry"Victoria Dye via GitGitGadget, Mar 17, 2022
  12. Derrick StoleeMar 21, 2022

Read the whole thread, see it on lore, or plain text.

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