threads / discuss / 7597

git-branch and git-remotes confusion

Subject: git-branch and git-remotes confusion

## tl;dr

3 messages between Apr 10, 2007 and Apr 10, 2007.

replies: 2people: 2as markdown or json

Martin Langhoff· Apr 10, 2007, 12:05 UTC · lore
Hi,

maybe I'm daft, or cogito has eaten my brain. The task at hand is really simple: clone from repo X, tracking branch Y (where branch Y != HEAD). The repo is http://git.catalyst.net.nz/git/moodle-r2.git , the branch is mdl18-olpc .

With cg, this is trivial:
  cg-clone http://git.catalyst.net.nz/git/moodle-r2.git#mdl18-olpc

which automagically gives me a "master" and "origin" pair of heads that do the right thing. Specifically, cg-update does the right thing.

With git 1.5.x, I managed to figure out that this is wrong. :
  git-clone --origin mdl18-olpc \
      http://git.catalyst.net.nz/git/moodle-r2.git
and now I am trying to see if some incantation around this works
   git-clone http://git.catalyst.net.nz/git/moodle-r2.git
   git-branch --track origin/mdl18-olpc my18-olpc

But it isn't working, and I'm reading git/Documentation for git-branch and git-remote but I can't find it. I don't care about any other branch (though if they are there, fine!). Is there a trivially simple answer.

(Cogito has eaten my brain probably. For a long time I've always cloned with cogito just for the sake of this convenience, even if I was going to use git mostly when working with the code. Now I'm working on a server that only has git, so I thought 1.5.x would make this trivial...)

cheers,
martin
Jeff King· Apr 10, 2007, 12:25 UTC · re: Martin Langhoff · lore

Re: git-branch and git-remotes confusion

On Wed, Apr 11, 2007 at 12:05:17AM +1200, Martin Langhoff wrote:
>   git-clone http://git.catalyst.net.nz/git/moodle-r2.git
>   git-branch --track origin/mdl18-olpc my18-olpc
Your arguments to git-branch are backwards. It should be:
  git-branch --track my18-olpc origin/mdl18-olpc

Also note that --track didn't show up until 1.5.1. Other than that, it should do what you expect (check out your .git/config before and after to see the impact of --track).

-Peff
Martin Langhoff· Apr 10, 2007, 12:33 UTC · re: Jeff King · lore

Re: git-branch and git-remotes confusion

On 4/11/07, Jeff King <peff@peff.net> wrote:
Show 7 quoted lines
> Your arguments to git-branch are backwards. It should be:
>
>   git-branch --track my18-olpc origin/mdl18-olpc
>
> Also note that --track didn't show up until 1.5.1.  Other than that, it
> should do what you expect (check out your .git/config before and after
> to see the impact of --track).

thanks. And I'm reading the doco for 1.5.latest and it turns out I'm using 1.5.0.5 so that won't work either.

hmmm. actually, I'm having another problem that is a bit more serious: cloning via http doesn't create a remotes/origin and doesn't perform the initial checkout.

will post separately about this...
martin

← back to recent threads