RE: git cloning paths

Hi Doug,

The method I have been using to achieve this is to create a wrapper script that does the following:

git clone -n # clone, but don't checkout cd <repo name> git config core.sparseCheckout true # configure sparse-checkout on # echo the list of bits you want into .git/info/sparse-checkout git checkout

Do watch out though, the interpretation of the sparse-checkout file has changed since git 1.7, I would suggest you use the latest git and record the git version as a comment in top of the sparse checkout file, in case it changes again. 

I hope this helps,

Caleb

-----Original Message-----
From: git-owner@vger.kernel.org [mailto:git-owner@vger.kernel.org] On Behalf Of Douglas Garstang
Sent: 12 July 2012 23:17
To: git@vger.kernel.org
Subject: git cloning paths

All,

I'm a relative newcomer to git and I've just inherited a setup where all of the company's code is in a single git repository. Within this repository are multiple projects. It seems that git doesn't natively allow cloning/checking out of individual paths within the repo (ie projects), which would seem to make integrating git with a continuous build system rather difficult. That is, the build system has to clone the entire repo, and therefore a change to any project will result in the entire contents of the repo being built.

Correct....?

Doug. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html