git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v4 1/4] clone: let the user know when check_everything_connected is run

From
Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Date
May 26, 2013, 01:16 UTC
Message-ID
<1369530977-12746-2-git-send-email-pclouds@gmail.com>
In-Reply-To
<1369530977-12746-1-git-send-email-pclouds@gmail.com>

check_everything_connected could take a long time, especially in the clone case where the whole DAG is traversed. The user deserves to know what's going on.

Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 builtin/clone.c | 4 ++++
 1 file changed, 4 insertions(+)
diff --git a/builtin/clone.c b/builtin/clone.c
index 035ab64..dad4265 100644
--- a/builtin/clone.c
+++ b/builtin/clone.c
@@ -546,8 +546,12 @@ static void update_remote_refs(const struct ref *refs,
 {
 	const struct ref *rm = mapped_refs;
 
+	if (0 <= option_verbosity)
+		printf(_("Checking connectivity... "));
 	if (check_everything_connected(iterate_ref_map, 0, &rm))
 		die(_("remote did not send all necessary objects"));
+	if (0 <= option_verbosity)
+		printf(_("done\n"));
 
 	if (refs) {
 		write_remote_refs(mapped_refs);
-- 
1.8.2.83.gc99314b
Previous: Nguyễn Thái Ngọc DuyNext: Nguyễn Thái Ngọc Duy
Message 2 of 5 in “nd/clone-connectivity-shortcut updates”
  1. 0/4 nd/clone-connectivity-shortcut updatesNguyễn Thái Ngọc Duy, May 26, 2013
  2. 1/4 clone: let the user know when check_everything_connected is runNguyễn Thái Ngọc Duy, May 26, 2013
  3. 2/4 fetch-pack: prepare updated shallow file before fetching the packNguyễn Thái Ngọc Duy, May 26, 2013
  4. 3/4 index-pack: remove dead code (it should never happen)Nguyễn Thái Ngọc Duy, May 26, 2013
  5. 4/4 clone: open a shortcut for connectivity checkNguyễn Thái Ngọc Duy, May 26, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.