projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 45fd8bd) | patch
Cloning from a repo without "current branch"
authorNanako Shiraishi <nanako3@bluebottle.com>
Sat, 16 Jun 2007 22:26:08 +0000 (15:26 -0700)
committerJunio C Hamano <gitster@pobox.com>
Wed, 20 Jun 2007 23:33:24 +0000 (16:33 -0700)
commit6762079a96dd18bcaab75f2d05034f7447434161
treeb145c14b68a17cf0b963c9acf3722e3e1de87832tree | snapshot
parent45fd8bd32dd68ce6b14a406d0abbd6f56490131ccommit | diff
Cloning from a repo without "current branch"

If the remote repository does not have a "current branch", git-clone
was confused and did not set up the resulting new repository
correctly.  It did not reset HEAD from the default 'master', and did
not write the SHA1 to the master branch.

Signed-off-by: Nanako Shiraishi <nanako3@bluebottle.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
git-clone.sh diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.