From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
To: Cory Fields <FOSS@atlastechnologiesinc.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
git@vger.kernel.org
Subject: Re: 'git replace' and pushing
Date: Fri, 26 Nov 2010 21:29:30 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.1.10.1011262114410.17721@debian> (raw)
In-Reply-To: <AANLkTi=FjSFLsbXf2Rp_Onm26yyxX+xSPrh2pB=_f5RU@mail.gmail.com>
On Fri, 26 Nov 2010, Cory Fields wrote:
> 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
next prev parent reply other threads:[~2010-11-27 2:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 4:33 'git replace' and pushing Cory Fields
2010-11-25 8:37 ` Michael J Gruber
2010-11-26 21:16 ` Cory Fields
2010-11-26 21:43 ` Jonathan Nieder
2010-11-26 23:18 ` Junio C Hamano
2010-11-27 1:58 ` Cory Fields
2010-11-26 20:29 ` Martin von Zweigbergk [this message]
2010-11-27 1:59 ` Cory Fields
2010-11-27 7:52 ` Jonathan Nieder
2010-11-27 17:54 ` Cory Fields
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=alpine.DEB.1.10.1011262114410.17721@debian \
--to=martin.von.zweigbergk@gmail.com \
--cc=FOSS@atlastechnologiesinc.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
/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).