git-clone.sh: properly configure remote even if remote's head is dangling
commit5274ba6907cc12d6e6556ff85cb0e4819bd3f730
authorGerrit Pape <pape@smarden.org>
Wed, 20 Feb 2008 15:10:17 +0000 (20 15:10 +0000)
committerJunio C Hamano <gitster@pobox.com>
Wed, 20 Feb 2008 19:31:17 +0000 (20 11:31 -0800)
tree93c31367c6441ef73c63ff028c3cd59f03d09456
parentfbd538c262b03d7b096e840a7ef0cdd54c5cea4f
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>
git-clone.sh
t/t5701-clone-local.sh