2009/8/11 Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx>: > One common source of confusion for newcomers is the fact that master is > given such a special treatment in git. While it is certainly okay and > helpful to set up a default branch in a new repository (git init) it is > not at all clear why it should be treated specially in any other > situation, such as: > > - Why is master the only local branch which git clone sets up (git > checkout -b master origin/master)? Because master is the default branch in the remote repository? [...] > This behaviour not only is hard to justify; in fact it gives users a > completely wrong impression: by pretending that master is special, It is not hard to justify (the git clone behavior). master is not special, it is just the default branch, but you can change it changing the HEAD symlink. > but > also by hiding core concepts (distinguishing local/remote branches, > detached heads) from the user at a point where that very hiding leads to > confusion. > > Under the hood, it is of course HEAD which is given special treatment > (and which in the majority of repos points to master), and git clone > sets up a local branch according to HEAD (and does some other guess work > when cloning bare repos), which means that git clone shows the same > "random" behaviour which git svn clone does: Which local branch is set > up by default depends on the current value of HEAD/most recent commit at > the time of the cloning operation. It's not random. And please don't mix the "git clone" and "git svn" case. > So, I suggest that starting with git 1.7: > > - git clone does not set up any local branches at all I think you should first think if this is going to really help newcomers. I think this would be worst. Instead of "why only 'master'?" the question will be "why I don't get any files in the workdir?" "git clone checks out the default branch, and this is 'master' by default" is not that hard. HTH, Santi -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html