git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Did I miss something? git-clone doesn't grab all branches????

From
TTTimur Tabi <timur@freescale.com>
Date
Mar 30, 2007, 17:03 UTC
Message-ID
<460D42FE.1080703@freescale.com>
In-Reply-To
<AF0367BA48C55940A43CCF08DF35553C0114148C@az33exm24.fsl.freescale.net>
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
Previous: Loeliger Jon-LOELIGERNext: Junio C Hamano
Message 3 of 4 in “Did I miss something? git-clone doesn't grab all branches????”
  1. Timur TabiMar 30, 2007
  2. Loeliger Jon-LOELIGERMar 30, 2007
  3. Timur TabiMar 30, 2007
  4. Junio C HamanoMar 31, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.