summaryrefslogtreecommitdiff
path: root/connected.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2016-07-15 10:32:28 (GMT)
committerJunio C Hamano <gitster@pobox.com>2016-07-20 19:11:09 (GMT)
commit70d5e2d77b4c2afdb442b37924bc252793e106d9 (patch)
treeb02b7cd7456c2ea0e388bbd42684c97a14bf0948 /connected.c
parente0331849a081fe4919f4130540165ce7d7355748 (diff)
downloadgit-70d5e2d77b4c2afdb442b37924bc252793e106d9.zip
git-70d5e2d77b4c2afdb442b37924bc252793e106d9.tar.gz
git-70d5e2d77b4c2afdb442b37924bc252793e106d9.tar.bz2
check_connected: add progress flag
Connectivity checks have to traverse the entire object graph in the worst case (e.g., a full clone or a full push). For large repositories like linux.git, this can take 30-60 seconds, during which time git may produce little or no output. Let's add the option of showing progress, which is taken care of by rev-list. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'connected.c')
-rw-r--r--connected.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/connected.c b/connected.c
index 5f5c8bd..8e3e4b1 100644
--- a/connected.c
+++ b/connected.c
@@ -58,6 +58,9 @@ int check_connected(sha1_iterate_fn fn, void *cb_data,
argv_array_push(&rev_list.args, "--not");
argv_array_push(&rev_list.args, "--all");
argv_array_push(&rev_list.args, "--quiet");
+ if (opt->progress)
+ argv_array_pushf(&rev_list.args, "--progress=%s",
+ _("Checking connectivity"));
rev_list.git_cmd = 1;
rev_list.in = -1;