Re: strange "git clone" behavior wrt an active branch
- From
- Santi Béjar <santi@agolina.net>
- Date
- Sep 28, 2008, 12:37 UTC
- Message-ID
- <adf1fd3d0809280537k7adffe3dte9579fe70c7f990e@mail.gmail.com>
- In-Reply-To
- <ee2a733e0809280505n69f62e0fy89667c175bcc16c@mail.gmail.com>
On Sun, Sep 28, 2008 at 2:05 PM, Leo Razoumov <slonik.az@gmail.com> wrote:
Show 13 quoted lines
> 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:
$ git ls-remote $url $sha1 HEAD $sha1 $branchname ...
instead of: ref: refs/heads/master HEAD $sha1 $branchname ...
So, I think it is a current limitation that maybe should be documented.
HTH, Santi