From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: git@vger.kernel.org
Subject: Re: Any tips for improving the performance of cloning large repositories?
Date: Fri, 16 Dec 2011 14:39:05 +0100 [thread overview]
Message-ID: <hbf.20111216zcin@bombur.uio.no> (raw)
In-Reply-To: <hbf.20111216yufz@bombur.uio.no>
I wrote:
> Do you often need to clone from a remote? Instead of cloning from a
> local (git clone --mirror) which gets auto-updated from the remote.
Er, obviously not, since you tried that with rsync. Create the mirror
with 'git clone --mirror', then update it with 'git fetch' rather than
rsync.
--
Hallvard
next prev parent reply other threads:[~2011-12-16 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 13:02 Any tips for improving the performance of cloning large repositories? Alex Bennee
2011-12-16 13:11 ` Hallvard Breien Furuseth
2011-12-16 13:39 ` Hallvard Breien Furuseth [this message]
2011-12-16 14:14 ` Seth Robertson
2011-12-16 15:28 ` Alex Bennee
2011-12-16 17:08 ` Junio C Hamano
2011-12-16 18:37 ` Alex Bennee
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=hbf.20111216zcin@bombur.uio.no \
--to=h.b.furuseth@usit.uio.no \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.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).