summaryrefslogtreecommitdiff
path: root/t/t4100/t-apply-4.patch
diff options
context:
space:
mode:
authorLibravatar Derrick Stolee <dstolee@microsoft.com>2019-11-25 21:28:23 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-11-27 10:57:10 +0900
commitecc0869080701b5e252f74ed7b3d0156a5ec6112 (patch)
treeab0c7d597eea5b39421bda9ad6176d439540438d /t/t4100/t-apply-4.patch
parentprogress: create GIT_PROGRESS_DELAY (diff)
downloadtgif-ecc0869080701b5e252f74ed7b3d0156a5ec6112.tar.xz
commit-graph: use start_delayed_progress()
When writing a commit-graph, we show progress along several commit walks. When we use start_delayed_progress(), the progress line will only appear if that step takes a decent amount of time. However, one place was missed: computing generation numbers. This is normally a very fast operation as all commits have been parsed in a previous step. But, this is showing up for all users no matter how few commits are being added. The tests that check for the progress output have already been updated to use GIT_PROGRESS_DELAY=0 to force the expected output. Helped-by: Jeff King <peff@peff.net> Reported-by: ryenus <ryenus@gmail.com> Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4100/t-apply-4.patch')
0 files changed, 0 insertions, 0 deletions