diff options
| author | Samuel Tardieu <sam@rfc1149.net> | 2008-03-09 12:37:55 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2008-03-12 05:13:16 (GMT) |
| commit | 3000658f7c15c880f976aac0ade73efd3b1e9790 (patch) | |
| tree | 37e335441ceec8e8320dfdde9eebda89b68f39f2 | |
| parent | 3b9dcff5df97ab642de48bc1ce781961686081aa (diff) | |
| download | git-3000658f7c15c880f976aac0ade73efd3b1e9790.zip git-3000658f7c15c880f976aac0ade73efd3b1e9790.tar.gz git-3000658f7c15c880f976aac0ade73efd3b1e9790.tar.bz2 | |
"remote update": print remote name being fetched from
When the other end has dangling symref, "git fetch" issues an error
message but that is not grave enough to cause the fetch process to fail.
As the result, the user will see something like this:
$ git remote update
error: refs/heads/2.0-uobjects points nowhere!
"remote update" used to report which remote it is fetching from, like
this:
$ git remote update
Updating core
Updating matthieu
error: refs/heads/2.0-uobjects points nowhere!
Updating origin
This reinstates the message "Updating <name>" in "git remote update".
Signed-off-by: Samuel Tardieu <sam@rfc1149.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| -rw-r--r-- | builtin-remote.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/builtin-remote.c b/builtin-remote.c index 637b904..24e6929 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; |