From: Timur Tabi Date: Fri, 30 Mar 2007 17:03:58 GMT Subject: Re: Did I miss something? git-clone doesn't grab all branches???? Message-ID: <460D42FE.1080703@freescale.com> In-Reply-To: Loeliger Jon-LOELIGER wrote: > Timur, > > You missed something. :-) You didn't read the Release > Notes for 1.5 that I forwarded. I didn't get that email. However, I did read the release notes for 1.5 on the web, and it didn't help. It's as if I'm on a different planet then everyone else who uses git, and so no one understands what I'm trying to do. I hate branches. I never use them. I create a whole new tree for each commit that I work on. So I like to have a clone of all of the main external repositories on my hard drive. Then I just clone these local repos into other trees on my hard drive. In the past, my clone of paulus/powerpc.git contained everything. Every time I did a git-pull, it would grab everything. Then I could do a local clone/checkout if I ever wanted to work on a branch (like for-2.6.22). I didn't have to know the names of the branches when I did git-clone. Because of the changes to git-clone, this process got a whole lot more complicated. Now I need to issue multiple commands for each branch. Ugh. > As a start, do this: > > git branch -a I think I figured it out, but I'm not sure it's working: git-clone http://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git powerpc.git cd powerpc.git git-checkout origin/for-2.6.22 git-checkout -b for-2.6.22 When I do this, git-branch -l shows: * for-2.6.22 master So I think I'm okay. -- Timur Tabi Linux Kernel Developer @ Freescale