]> git.ipfire.org Git - thirdparty/git.git/commit - t/t6500-gc.sh
commit-graph: use start_delayed_progress()
authorDerrick Stolee <dstolee@microsoft.com>
Mon, 25 Nov 2019 21:28:23 +0000 (21:28 +0000)
committerJunio C Hamano <gitster@pobox.com>
Wed, 27 Nov 2019 01:57:10 +0000 (10:57 +0900)
commitecc0869080701b5e252f74ed7b3d0156a5ec6112
treeab0c7d597eea5b39421bda9ad6176d439540438d
parent44a4693bfcec1876b29cdaec3625819d80ea1280
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>
commit-graph.c
t/t6500-gc.sh