From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
To: "João Paulo Melo de Sampaio" <jpmelos@gmail.com>
Cc: GIT Mailing List <git@vger.kernel.org>
Subject: Re: Remote branchs -- how can I check them out?
Date: Sun, 30 Jan 2011 19:05:57 +0300 [thread overview]
Message-ID: <20110130160556.GI5713@localhost.localdomain> (raw)
In-Reply-To: <AANLkTin3Tfcf=WJHJdSA9TwhFXQfaMrnm5+YEWWjo=qj@mail.gmail.com>
On Sun, Jan 30, 2011 at 01:05:07PM -0200, João Paulo Melo de Sampaio wrote:
> When I just cloned git using
>
> git clone git://git.kernel.org/pub/scm/git/git.git
>
> and I type
>
> git branch
>
> it shows me I have only the 'master' branch in my local repository
>
> * master
>
> and when I type
>
> git branch -a
>
> it shows that there's all these branches remotely
>
> * master
> remotes/origin/HEAD -> origin/master
> remotes/origin/html
> remotes/origin/maint
> remotes/origin/man
> remotes/origin/master
> remotes/origin/next
> remotes/origin/pu
> remotes/origin/todo
>
> What do I have to do to be able to see what's in the 'maint', 'next'
> and 'todo' branches, for example?
These branches are local to your repository. They are "remote" in the
sense you're not supposed to modify them directly.
So to inspect such a branch just use its full name ("origin/next" for
instance) when working with commands like git-log.
See [1], [2] for more info.
Also your question appears to be quite basic which hints at that you did
not read a good book on Git before using it. So starting at [3] is
recommended -- it mentions a bunch of good books and manuals (some of
which are available freely).
1. http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#examining-remote-branches
2. http://progit.org/book/ch3-5.html
3. http://git-scm.com/documentation
next prev parent reply other threads:[~2011-01-30 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 15:05 Remote branchs -- how can I check them out? João Paulo Melo de Sampaio
2011-01-30 16:05 ` Konstantin Khomoutov [this message]
2011-01-30 21:32 ` [RFC/PATCH 0/2] " Jonathan Nieder
2011-01-30 21:33 ` [PATCH 1/2] Documentation/branch: split description into subsections Jonathan Nieder
2011-01-31 1:55 ` Sverre Rabbelier
2011-01-30 21:35 ` [PATCH 2/2] Documentation/branch: briefly explain what a branch is Jonathan Nieder
2011-01-31 2:51 ` Junio C Hamano
2011-01-31 0:35 ` [RFC/PATCH 0/2] Re: Remote branchs -- how can I check them out? João Paulo Melo de Sampaio
2011-01-30 16:35 ` Jakub Narebski
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=20110130160556.GI5713@localhost.localdomain \
--to=flatworm@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=jpmelos@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.