aboutsummaryrefslogtreecommitdiff
path: root/Makefile
diff options
context:
space:
mode:
authorSamuel Tardieu <sam@rfc1149.net>2008-03-09 13:37:55 +0100
committerJunio C Hamano <gitster@pobox.com>2008-03-11 22:13:16 -0700
commit3000658f7c15c880f976aac0ade73efd3b1e9790 (patch)
tree37e335441ceec8e8320dfdde9eebda89b68f39f2 /Makefile
parent3b9dcff5df97ab642de48bc1ce781961686081aa (diff)
downloadgit-3000658f7c15c880f976aac0ade73efd3b1e9790.tar.gz
git-3000658f7c15c880f976aac0ade73efd3b1e9790.tar.xz
"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>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions