Re: Organizing (large) test data in git

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 27, 2007, 20:22 UTC
Message-ID: <Pine.LNX.4.63.0702272119430.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <17892.37416.358405.211524@lisa.zopyra.com>

Hi,

On Tue, 27 Feb 2007, Bill Lear wrote:

Show 18 quoted lines

> On Tuesday, February 27, 2007 at 21:14:07 (+0100) Johannes Schindelin writes:
> >> 
> >> Welll... it's not really a matter of capacity, though I do agree that
> >> lifting that limit will help.  We are more concerned with time to
> >> clone the repos over the (often very slow) corporate network, for
> >> example.  With future ratios of about 1% code to 99% test data, we
> >> hither and yon with little care, and a monster data repo that is
> >> (somehow) sanely managed with git as well.  I was just curious if
> >> others had run into the management problems that I mentioned with
> >> separating test data from code and what they may have done to surmount
> >> them.
> >
> >Okay I misunderstood, then.
> >
> >Do shallow clones help you?
> 
> Hmm, can't answer now, since I don't know what these are.  I shall
> investigate and see if they do.

Basically, shallow clones cut off branches at some point, even if those commits have references to their parents.

For example, if you have a linear branch HEAD~1000..HEAD, and you want to get just the latest two commits, a shallow clone will give you just HEAD~1..HEAD, pretending that HEAD~1 is a root commit (a commit without parents), when it is not.

But if you do not care for history, instead just for being up-to-date, it should help you.

Ciao, Dscho

P.S.: And no, I don't remember if you need to say "--depth 2" or "--depth 1" for that... Sorry