From: Jeff King <peff@peff.net>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Quick way to clone exactly one branch
Date: Thu, 28 May 2009 16:15:03 -0400 [thread overview]
Message-ID: <20090528201503.GL13499@coredump.intra.peff.net> (raw)
In-Reply-To: <32541b130905201345h6daa84e8hb937e1e46456b3c5@mail.gmail.com>
On Wed, May 20, 2009 at 04:45:44PM -0400, Avery Pennarun wrote:
> Is there a quick alternative to the following?
>
> mkdir myproj
> cd myproj
> git init
> git fetch git://whatever master
> git checkout -b master FETCH_HEAD
>
> Basically, the above is a lot like 'git clone' but only clones the
> 'master' branch. For really big projects with lots of junk in other
> branches, the above can save a lot of bandwidth.
No, AFAIK there isn't a simpler way to do it. But it is something people
have asked about before, so I think it would be a nice addition.
You can't even use "git remote" because it doesn't allow you to tweak
the refspecs you add. To do it "just like clone" I think you would have
to:
git config remote.origin.url git://whatever
git config remote.origin.fetch refs/heads/master:refs/remotes/origin/master
It would be nice if that could be:
git remote add -b master origin git://whatever
and then make it available as:
git clone -b master git://whatever
Multiple "-b <branch>" options would generate refspecs to pull multiple
branches. You could even allow "git clone --refspec=<whatever>", but I
don't know what you would use that much flexibility for (and at that
point, you are probably comfortable enough to write the config
yourself).
-Peff
next prev parent reply other threads:[~2009-05-28 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 20:45 Quick way to clone exactly one branch Avery Pennarun
2009-05-28 20:15 ` Jeff King [this message]
2009-05-28 20:26 ` Jakub Narebski
2009-05-28 20:32 ` 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=20090528201503.GL13499@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).