| commit | 3000658f7c15c880f976aac0ade73efd3b1e9790 | |
| author | Samuel Tardieu <sam@rfc1149.net> | |
| Sun, 9 Mar 2008 12:37:55 +0000 (9 13:37 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 12 Mar 2008 05:13:16 +0000 (11 22:13 -0700) | ||
| tree | 37e335441ceec8e8320dfdde9eebda89b68f39f2 | treesnapshot (tar.gz zip) |
| parent | 3b9dcff5df97ab642de48bc1ce781961686081aa | commitdiff |
"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>
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>
| builtin-remote.c | diffblobblamehistory |