summaryrefslogtreecommitdiff
path: root/t/t3002-ls-files-dashpath.sh
diff options
context:
space:
mode:
authorLibravatar Gerrit Pape <pape@smarden.org>2008-02-20 15:10:17 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2008-02-20 11:31:17 -0800
commit5274ba6907cc12d6e6556ff85cb0e4819bd3f730 (patch)
tree93c31367c6441ef73c63ff028c3cd59f03d09456 /t/t3002-ls-files-dashpath.sh
parentDocumentation/git-stash: document options for git stash list (diff)
downloadtgif-5274ba6907cc12d6e6556ff85cb0e4819bd3f730.tar.xz
git-clone.sh: properly configure remote even if remote's head is dangling
When cloning a remote repository which's HEAD refers to a nonexistent ref, git-clone cloned all existing refs, but failed to write the configuration for 'remote'. Now it detects the dangling remote HEAD, refuses to checkout any local branch since HEAD refers to nowhere, but properly writes the configuration for 'remote', so that subsequent 'git fetch's don't fail. The problem was reported by Daniel Jacobowitz through http://bugs.debian.org/466581 Signed-off-by: Gerrit Pape <pape@smarden.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3002-ls-files-dashpath.sh')
0 files changed, 0 insertions, 0 deletions