summaryrefslogtreecommitdiffstats
path: root/builtin/commit.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2018-10-16 09:15:58 +0200
committerJunio C Hamano <gitster@pobox.com>2018-10-16 09:15:58 +0200
commit36d767d02e12c1ff991511b7bd8c1d023340f2ca (patch)
tree028b22c2a0761e229d9c02e29870d2009e274bfa /builtin/commit.c
parentThird batch for 2.20 (diff)
parentgc: fix regression in 7b0f229222 impacting --quiet (diff)
downloadgit-36d767d02e12c1ff991511b7bd8c1d023340f2ca.tar.xz
git-36d767d02e12c1ff991511b7bd8c1d023340f2ca.zip
Merge branch 'ab/commit-graph-progress'
Generation of (experimental) commit-graph files have so far been fairly silent, even though it takes noticeable amount of time in a meaningfully large repository. The users will now see progress output. * ab/commit-graph-progress: gc: fix regression in 7b0f229222 impacting --quiet commit-graph verify: add progress output commit-graph write: add progress output
Diffstat (limited to 'builtin/commit.c')
-rw-r--r--builtin/commit.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/builtin/commit.c b/builtin/commit.c
index b57d8e4b82..3f33ae6043 100644
--- a/builtin/commit.c
+++ b/builtin/commit.c
@@ -1654,7 +1654,7 @@ int cmd_commit(int argc, const char **argv, const char *prefix)
"not exceeded, and then \"git reset HEAD\" to recover."));
if (git_env_bool(GIT_TEST_COMMIT_GRAPH, 0))
- write_commit_graph_reachable(get_object_directory(), 0);
+ write_commit_graph_reachable(get_object_directory(), 0, 0);
rerere(0);
run_command_v_opt(argv_gc_auto, RUN_GIT_CMD);