On Thu, Aug 9, 2012 at 11:17 AM, THUFIR HAWAT <hawat.thu...@gmail.com> wrote:
>
>
> On Wednesday, 8 August 2012 20:55:31 UTC-7, Aneesh wrote:
>>
>> [..]
>>
>> > and a few variants, I can't find the syntax in "git help clone"
>>
>> 'git clone -b <branchname> ...' basically means to checkout
>> <branchname> (in a non-bare repository), instead of whatever was being
>> pointed to by HEAD in the cloned repository. This does NOT mean that
>> git will get only the <branchname> branch and not others...
>>
>> After cloning, just to 'git branch -r' to see a list of all
>> remote-tracking branches - i.e. all branches that existed in the
>> cloned repo when you had cloned it...
>>
>> Hope that helps..
>>
>> regards,
>> Aneesh
>
>
> hmm, so after you clone a repo, what's the effective difference between
> "checkout foo" and "checkout -b foo"?
>
> git help doesn't help me with that:
>
>            If -b is given, a new branch is created as if git-branch(1) were
> called and
>            then checked out; in this case you can use the --track or
> --no-track options,
>            which will be passed to git branch. As a convenience, --track
> without -b
>            implies branch creation; see the description of --track below.
>
>
>  if branch "foo" doesn't exist, the checkout will fail?  You can't
> accidentally get name collisions between local foo and remote foo?
>
>

This link should help - has basically the same query..

http://stackoverflow.com/questions/67699/how-do-i-clone-all-remote-branches-with-git

regards,
Aneesh

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to