summaryrefslogtreecommitdiff
path: root/t/t4119-apply-config.sh
diff options
context:
space:
mode:
authorLibravatar Derrick Stolee <dstolee@microsoft.com>2021-12-20 14:48:11 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-12-20 11:59:17 -0800
commit47ca93d0710c114b61b3079d3b88d2d7528f5666 (patch)
tree3bedae9ab0e65290fee82f70c71cce8c5f24f161 /t/t4119-apply-config.sh
parentrepack: respect kept objects with '--write-midx -b' (diff)
downloadtgif-47ca93d0710c114b61b3079d3b88d2d7528f5666.tar.xz
repack: make '--quiet' disable progress
While testing some ideas in 'git repack', I ran it with '--quiet' and discovered that some progress output was still shown. Specifically, the output for writing the multi-pack-index showed the progress. The 'show_progress' variable in cmd_repack() is initialized with isatty(2) and is not modified at all by the '--quiet' flag. The '--quiet' flag modifies the po_args.quiet option which is translated into a '--quiet' flag for the 'git pack-objects' child process. However, 'show_progress' is used to directly send progress information to the multi-pack-index writing logic which does not use a child process. The fix here is to modify 'show_progress' to be false if po_opts.quiet is true, and isatty(2) otherwise. This new expectation simplifies a later condition that checks both. Update the documentation to make it clear that '-q' will disable all progress in addition to ensuring the 'git pack-objects' child process will receive the flag. Use 'test_terminal' to check that this works to get around the isatty(2) check. Helped-by: Jeff King <peff@peff.net> Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4119-apply-config.sh')
0 files changed, 0 insertions, 0 deletions