summaryrefslogtreecommitdiff
path: root/t/t8009-blame-vs-topicbranches.sh
diff options
context:
space:
mode:
authorLibravatar SZEDER Gábor <szeder.dev@gmail.com>2020-07-10 21:02:38 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-07-15 11:57:19 -0700
commit862aead24eaf797860fb503561a1f86adf557abb (patch)
treece9c46dbeb1afc25a8152f06219c15b16d8eea53 /t/t8009-blame-vs-topicbranches.sh
parentcommit-graph: drop COMMIT_GRAPH_WRITE_CHECK_OIDS flag (diff)
downloadtgif-862aead24eaf797860fb503561a1f86adf557abb.tar.xz
commit-graph: fix "Collecting commits from input" progress line
To display a progress line while reading commits from standard input and looking them up, 5b6653e523 (builtin/commit-graph.c: dereference tags in builtin, 2020-05-13) should have added a pair of start_delayed_progress() and stop_progress() calls around the loop reading stdin. Alas, the stop_progress() call ended up at the wrong place, after write_commit_graph(), which does all the commit-graph computation and writing, and has several progress lines of its own. Consequently, that new Collecting commits from input: 1234 progress line is overwritten by the first progress line shown by write_commit_graph(), and its final "done" line is shown last, after everything is finished: $ { sleep 3 ; git rev-list -3 HEAD ; sleep 1 ; } | ~/src/git/git commit-graph write --stdin-commits Expanding reachable commits in commit graph: 873402, done. Writing out commit graph in 4 passes: 100% (3493608/3493608), done. Collecting commits from input: 3, done. Furthermore, that stop_progress() call was added after the 'cleanup' label, where that loop reading stdin jumps in case of an error. In case of invalid input this then results in the "done" line shown after the error message: $ { sleep 3 ; git rev-list -3 HEAD ; echo junk ; } | ~/src/git/git commit-graph write --stdin-commits error: unexpected non-hex object ID: junk Collecting commits from input: 3, done. Move that stop_progress() call to the right place. While at it, drop the unnecessary 'if (progress)' condition protecting the stop_progress() call, because that function is prepared to handle a NULL progress struct. Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com> Reviewed-by: Derrick Stolee <stolee@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t8009-blame-vs-topicbranches.sh')
0 files changed, 0 insertions, 0 deletions