threads / discuss / 12604

Unclear error message in "git remote update"

Subject: Unclear error message in "git remote update"

## tl;dr

3 messages between Mar 9, 2008 and Mar 12, 2008.

replies: 2people: 3as markdown or json

Samuel Tardieu· Mar 9, 2008, 12:37 UTC · lore

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
Johannes Schindelin· Mar 9, 2008, 20:52 UTC · re: Samuel Tardieu · lore

Re: Unclear error message in "git remote update"

Hi,
On Sun, 9 Mar 2008, Samuel Tardieu wrote:
Show 19 quoted lines
> 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?
None from me.

Thanks, Dscho

Junio C Hamano· Mar 12, 2008, 05:10 UTC · re: Samuel Tardieu · lore

Re: Unclear error message in "git remote update"

Samuel Tardieu <sam@rfc1149.net> writes:
Show 19 quoted lines
> 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?

I do not have objections, but it feels that the message for normal case (success) is cluttering the output.

If the remote repository is in a bad shape to solicit a "points nowhere" error, perhaps

 (1) that error message should be squelched out completely, as it does not
     affect the outcome of the fetch anyway, or
 (2) the dangling symref should cause "fetch" to error out but with a
     different error status than the total failure case, so that this
     caller can tell it is a non-grave error, or
 (3) the dangling symref should actually make the fetch fail, as the
     remote repository is corrupt.

For now I'll take your patch, but this is something we may want to clean-up in 1.6.0 timeframe.

← back to recent threads