summaryrefslogtreecommitdiff
path: root/t/t7111-reset-table.sh
diff options
context:
space:
mode:
authorLibravatar Derrick Stolee <dstolee@microsoft.com>2021-12-20 14:48:10 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-12-20 11:58:31 -0800
commite4d0c11c04ec3c28922168844ae2694e0d015b4e (patch)
treeffb8922a1c92f61deb456b201a6337b029ebeaf3 /t/t7111-reset-table.sh
parentGit 2.34.1 (diff)
downloadtgif-e4d0c11c04ec3c28922168844ae2694e0d015b4e.tar.xz
repack: respect kept objects with '--write-midx -b'
Historically, we needed a single packfile in order to have reachability bitmaps. This introduced logic that when 'git repack' had a '-b' option that we should stop sending the '--honor-pack-keep' option to the 'git pack-objects' child process, ensuring that we create a packfile containing all reachable objects. In the world of multi-pack-index bitmaps, we no longer need to repack all objects into a single pack to have valid bitmaps. Thus, we should continue sending the '--honor-pack-keep' flag to 'git pack-objects'. The fix is very simple: only disable the flag when writing bitmaps but also _not_ writing the multi-pack-index. This opens the door to new repacking strategies that might want to keep some historical set of objects in a stable pack-file while only repacking more recent objects. To test, create a new 'test_subcommand_inexact' helper that is more flexible than 'test_subcommand'. This allows us to look for the --honor-pack-keep flag without over-indexing on the exact set of arguments. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t7111-reset-table.sh')
0 files changed, 0 insertions, 0 deletions