If you somehow manage to do the initial clone, you can later on
configure a sparse checkout:


On Nov 17, 3:08 am, Konstantin Khomoutov <khomou...@gmail.com> wrote:
> On Nov 16, 2:20 am, vfclists <vfcli...@gmail.com> wrote:
> > If you want to work with only a few of the branches of a remote
> > repository, how to you clone it in a way which does not bring down
> > everything?
> I think it's impossible.
> But you should maybe rethink your approach to this.
> First, what you requested could only spare you bandwidth and disk
> space if the branches contain really divergent histories; for a
> typical project it is not true -- the branches tend to share vast
> amounts of history (hence bringing only few of them in would anyway
> bring most of the history), and if they don't, then you should
> probably look at submodules [1].
> The next thing to consider is "shallow cloning" -- see this FAQ entry
> [2].
> 1.http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html
> 2.https://git.wiki.kernel.org/index.php/GitFaq#How_do_I_use_git_for_lar...

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to