summaryrefslogtreecommitdiff
path: root/t/t6500-gc.sh
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2015-09-28 14:01:25 (GMT)
committerJunio C Hamano <gitster@pobox.com>2015-10-08 19:42:06 (GMT)
commit14886b40c552d3ad4d5492d922948d76762af198 (patch)
tree9cc35d6373299ae26e6e37bdba01ec4c2688873b /t/t6500-gc.sh
parent8c845cde99dcfc9821f1182623248dee9ebb4227 (diff)
downloadgit-14886b40c552d3ad4d5492d922948d76762af198.zip
git-14886b40c552d3ad4d5492d922948d76762af198.tar.gz
git-14886b40c552d3ad4d5492d922948d76762af198.tar.bz2
pack-objects: do not get distracted by broken symrefs
It is quite possible for, say, a remote HEAD to become broken, e.g. when the default branch was renamed. We should still be able to pack our objects when such a thing happens; simply ignore broken symrefs (because they cannot matter for the packing process anyway). This fixes https://github.com/git-for-windows/git/issues/423 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t6500-gc.sh')
-rwxr-xr-xt/t6500-gc.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/t/t6500-gc.sh b/t/t6500-gc.sh
index ed22dcc..5d7d414 100755
--- a/t/t6500-gc.sh
+++ b/t/t6500-gc.sh
@@ -30,7 +30,7 @@ test_expect_success 'gc -h with invalid configuration' '
test_i18ngrep "[Uu]sage" broken/usage
'
-test_expect_failure 'gc is not aborted due to a stale symref' '
+test_expect_success 'gc is not aborted due to a stale symref' '
git init remote &&
(
cd remote &&