git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Leo Razoumov" <slonik.az@gmail.com>
To: "Santi Béjar" <santi@agolina.net>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: strange "git clone" behavior wrt an active branch
Date: Sun, 28 Sep 2008 09:23:47 -0400	[thread overview]
Message-ID: <ee2a733e0809280623i30a9e298i30db2a84b8530d61@mail.gmail.com> (raw)
In-Reply-To: <adf1fd3d0809280537k7adffe3dte9579fe70c7f990e@mail.gmail.com>

On 9/28/08, Santi Béjar <santi@agolina.net> wrote:
> 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--

  reply	other threads:[~2008-09-28 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28 12:05 strange "git clone" behavior wrt an active branch Leo Razoumov
2008-09-28 12:37 ` Santi Béjar
2008-09-28 13:23   ` Leo Razoumov [this message]
2008-09-28 19:43     ` Santi Béjar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ee2a733e0809280623i30a9e298i30db2a84b8530d61@mail.gmail.com \
    --to=slonik.az@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=santi@agolina.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).