summaryrefslogtreecommitdiff
path: root/git-ls-remote.sh
diff options
context:
space:
mode:
authorNicolas Pitre <nico@cam.org>2006-12-18 20:16:58 (GMT)
committerJunio C Hamano <junkio@cox.net>2006-12-18 23:31:28 (GMT)
commitb3d9899324af174ff123498b5c7ded3749aac2bc (patch)
treea989a00d3ec4a50a281f29c980101ac3d2a4144a /git-ls-remote.sh
parent57b73150c4f1dbc26474a0031f433fb34db1c13f (diff)
downloadgit-b3d9899324af174ff123498b5c7ded3749aac2bc.zip
git-b3d9899324af174ff123498b5c7ded3749aac2bc.tar.gz
git-b3d9899324af174ff123498b5c7ded3749aac2bc.tar.bz2
make git a bit less cryptic on fetch errors
The remote server might not want to tell why it doesn't like us for security reasons, but let's make the client report such error in a bit less confusing way. The remote failure remains a mystery, but the local message might be a bit less so. [jc: with a gentle wording updates from Andy Parkins] Signed-off-by: Nicolas Pitre <nico@cam.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'git-ls-remote.sh')
-rwxr-xr-xgit-ls-remote.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/git-ls-remote.sh b/git-ls-remote.sh
index 0f88953..03b624e 100755
--- a/git-ls-remote.sh
+++ b/git-ls-remote.sh
@@ -94,7 +94,7 @@ while read sha1 path
do
case "$sha1" in
failed)
- die "Failed to find remote refs"
+ exit 1 ;;
esac
case "$path" in
refs/heads/*)