Re: 'git replace' and pushing

From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Date: Nov 26, 2010, 20:29 UTC
Message-ID: <alpine.DEB.1.10.1011262114410.17721@debian>
In-Reply-To: <AANLkTi=FjSFLsbXf2Rp_Onm26yyxX+xSPrh2pB=_f5RU@mail.gmail.com>

On Fri, 26 Nov 2010, Cory Fields wrote:

Show 5 quoted lines

> A shallow clone does not fit for us, because we want the default clone
> to only pull half.
> Having a public 1gb repository that will be cloned quite often is
> bound to make our host
> unhappy, so we're doing everything we can to get the size down.

At the GitTogether last month, my colleague brought up the subject of how to cope with repositories growing over time. The conclusion from the discussions was that shallow clones would proabably be the best option in general. FYI, even though it may not help you right now, having a default shallow clone depth configured in the repository on the server was also discussed.

/Martin