Re: strange "git clone" behavior wrt an active branch

From: Leo Razoumov <slonik.az@gmail.com>
Date: Sep 28, 2008, 13:23 UTC
Message-ID: <ee2a733e0809280623i30a9e298i30db2a84b8530d61@mail.gmail.com>
In-Reply-To: <adf1fd3d0809280537k7adffe3dte9579fe70c7f990e@mail.gmail.com>

On 9/28/08, Santi Béjar <santi@agolina.net> wrote:

Show 19 quoted lines

> On Sun, Sep 28, 2008 at 2:05 PM, Leo Razoumov <slonik.az@gmail.com> wrote:
>  > Hi All,
>  > I am using the latest stable version git-1.6.0.2.
>  >
>  > The man page for git-clone states explicitly that "git clone"
>  >
>  > " Clones a repository into a newly created directory, ...[snip]...
>  >  and creates and checks out an initial branch equal to the
>  >  cloned repository's currently active branch. "
>  >
>  > I noticed that while my active branch "My" happens to point to the
>  > same commit as the "master" the git clone will check out master
>  > instead of My (currently active branch). Is it a bug?
>  >
>
>
> Currently it is only guessed which is the active branch (with a
>  preference for the master branch as it is the default), as the current
>  protocol does not allow tranfering the ref links:

This is quite unfortunate design decision. There can be any number of local branches referring to the same commit. Without being able to pick into .git/HEAD it is impossible to decide which of them is "active".

--Leo--