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

Unclear error message in "git remote update"

From
Samuel Tardieu <sam@rfc1149.net>
Date
Mar 9, 2008, 12:37 UTC
Message-ID
<2008-03-09-13-37-55+trackit+sam@rfc1149.net>

One of my colleague seems to have destroyed one of its head in his private repository. When fetching from it through "git remote update" using next, the repository name is not output:

% git remote update error: refs/heads/2.0-uobjects points nowhere!

Using master, I get:

% git remote update Updating core Updating matthieu error: refs/heads/2.0-uobjects points nowhere! Updating origin

which is IMO much clearer. Also, I like seeing what remote repository it is updating from in case anything gets stuck or slow.

Any objection to reinstating the message as does the following patch?
From: Samuel Tardieu <sam@rfc1149.net>
Date: Sun, 9 Mar 2008 13:33:44 +0100
Subject: [PATCH] builtin remote update: print remote name being fetched from
Reinstate the message "Updating <name>" in git remote update.
Signed-off-by: Samuel Tardieu <sam@rfc1149.net>
---
 builtin-remote.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/builtin-remote.c b/builtin-remote.c
index ca3bf26..65d90e1 100644
--- a/builtin-remote.c
+++ b/builtin-remote.c
@@ -46,6 +46,7 @@ static int opt_parse_track(const struct option *opt, const char *arg, int not)
 static int fetch_remote(const char *name)
 {
 	const char *argv[] = { "fetch", name, NULL };
+	printf("Updating %s\n", name);
 	if (run_command_v_opt(argv, RUN_GIT_CMD))
 		return error("Could not fetch %s", name);
 	return 0;
-- 
1.5.4.3.611.g29c00
Next: Johannes Schindelin
Message 1 of 3 in “Unclear error message in "git remote update"”
  1. Samuel TardieuMar 9, 2008
  2. Johannes SchindelinMar 9, 2008
  3. Junio C HamanoMar 12, 2008

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.