summaryrefslogtreecommitdiff
path: root/progress.c
diff options
context:
space:
mode:
authorDerrick Stolee <dstolee@microsoft.com>2021-07-14 13:12:39 (GMT)
committerJunio C Hamano <gitster@pobox.com>2021-07-14 20:42:49 (GMT)
commitf8fe49e53958f19b0e62e9549a80fcaa56d2f3cf (patch)
tree79898035fb5a4f14216204fd0e984754a23bacea /progress.c
parentfe0d576153117953189e03d6c2c09445ccad4977 (diff)
downloadgit-f8fe49e53958f19b0e62e9549a80fcaa56d2f3cf.zip
git-f8fe49e53958f19b0e62e9549a80fcaa56d2f3cf.tar.gz
git-f8fe49e53958f19b0e62e9549a80fcaa56d2f3cf.tar.bz2
fsmonitor: integrate with sparse index
If we need to expand a sparse-index into a full one, then the FS Monitor bitmap is going to be incorrect. Ensure that we start fresh at such an event. While this is currently a performance drawback, the eventual hope of the sparse-index feature is that these expansions will be rare and hence we will be able to keep the FS Monitor data accurate across multiple Git commands. These tests are added to demonstrate that the behavior is the same across a full index and a sparse index, but also that file modifications to a tracked directory outside of the sparse cone will trigger ensure_full_index(). Reviewed-by: Elijah Newren <newren@gmail.com> Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'progress.c')
0 files changed, 0 insertions, 0 deletions