![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Gerrit Pape <pape@smarden.org> | |
| Wed, 20 Feb 2008 15:10:17 +0000 (15:10 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 20 Feb 2008 19:31:17 +0000 (11:31 -0800) | ||
| commit | 5274ba6907cc12d6e6556ff85cb0e4819bd3f730 | |
| tree | 93c31367c6441ef73c63ff028c3cd59f03d09456 | tree | snapshot |
| parent | fbd538c262b03d7b096e840a7ef0cdd54c5cea4f | commit | diff |
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>
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 | diff | blob | history | |
| t/t5701-clone-local.sh | diff | blob | history |