From: Jakub Narebski <jnareb@gmail.com>
To: "Sudipta GHOSH" <sudipta.in@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: remote branch checkout issue, why its *(no branch)
Date: Fri, 28 Nov 2008 14:32:56 -0800 (PST) [thread overview]
Message-ID: <m3k5anjxcd.fsf@localhost.localdomain> (raw)
In-Reply-To: <9e6474ae0811281415n7b4596afq7b3ce25816d9a639@mail.gmail.com>
"Sudipta GHOSH" <sudipta.in@gmail.com> writes:
> In our git repository there are few branches like
>
> master
> origin/B1
> origin/B2
>
> After doing #git checkout origin/B1 I found that my current branch is
> *(no branch)
>
> #git branch
> *(no branch)
> master
>
> Why its showing *(no branch) why not origin/B1
>
> How I can checkout origin/B1 and after that my current branch will be
> origin/B1 not the *(no branch)
First, 'origin/B1' is so called remote-tracking branch, and its full
name is refs/remotes/origin/B1. Those branches are updated
_automatically_ by git on fetch, to follow branch 'B1' in 'origin'
repository. Therefore, to not lose _your_ changes git doesn't allow
checking out remote-tracking branches. You can checkout _state_ of
such branch into anonymous noname branch, so called in git jargon
"detached HEAD".
What you can do is to create _local_ branch, closely tied to
remote-tracking branch 'origin/B1', by using:
$ git branch -b B1 --track origin/B1
Git would set up configuration for this branch in such way that "git
pull" command given on 'B1' branch would "do the right thing"(TM)
I really recommend reading "Git User's Manual" or "The Git Community
Book" first...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-11-28 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 22:15 remote branch checkout issue, why its *(no branch) Sudipta GHOSH
2008-11-28 22:32 ` Jakub Narebski [this message]
2008-11-28 23:24 ` Björn Steinbrink
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=m3k5anjxcd.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=sudipta.in@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.