Git development
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Jeff King <peff@peff.net>
Cc: Martin Langhoff <martin.langhoff@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git-branch, older repos and more confusion
Date: Thu, 12 Apr 2007 16:54:56 +1200	[thread overview]
Message-ID: <461DBBA0.3070609@vilain.net> (raw)
In-Reply-To: <20070412042308.GA22539@coredump.intra.peff.net>

Jeff King wrote:
>> Alas - I think support for it seems to be going the away... what I am
>> missing is a clear way to say git-clone <repo>#branch that has the
>> same properties that `cg-clone <repo>#branch` has. Namely, once you
>> are done, there are clear names for your "local tip" and "remote tip",
>> and push and pull do the right thing without extra params.
>>     
>
> I don't think there is a way to clone _just_ that branch, but if you're
> OK with fetching all of the branches, then you should be able to do
> just:
>
> git-clone <repo>
> git-branch --track branch origin/branch
> git-checkout branch
>   

You can;

 mkdir moodle
 cd moodle
 git-init
 git-remote add -t mdl-topnz -f origin \
    git://git.catalyst.net.nz/moodle.git

But yes, not as easy as "cg-clone git://...#branch"

I sent a patch for 'git remote prune -c' recently that would help in the
transition between the two remotes formats.

Sam.

  reply	other threads:[~2007-04-12  4:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12  4:14 git-branch, older repos and more confusion Martin Langhoff
2007-04-12  4:23 ` Jeff King
2007-04-12  4:54   ` Sam Vilain [this message]
2007-04-12  5:06     ` Martin Langhoff
2007-04-12  5:05   ` Martin Langhoff
2007-04-12  5:21     ` Jeff King
2007-04-12  6:00       ` Martin Langhoff
2007-04-12  6:16         ` Martin Langhoff
2007-04-12  6:22         ` Jeff King

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=461DBBA0.3070609@vilain.net \
    --to=sam@vilain.net \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    --cc=peff@peff.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox