From: James Cloos <cloos@jhcloos.com>
To: Zenaan Harkness <zen@freedbms.net>
Cc: git@vger.kernel.org
Subject: Re: git fails on large repo clone on intermittent, or intermittently-high-latency, connections
Date: Sun, 09 Jan 2011 15:04:55 -0500 [thread overview]
Message-ID: <m38vyt7shs.fsf@jhcloos.com> (raw)
In-Reply-To: <AANLkTinkhmHpAQjraviKjqFAczThR5GtT_qdyf6Sb3nm@mail.gmail.com> (Zenaan Harkness's message of "Thu, 6 Jan 2011 01:28:40 +1100")
In addition to the other replies, if you have a shell login elswhere you
can clone there, bundle the file, and use rsync, http, ftp or the like
to copy it down.
If the remote site's git is too old to have git bundle, use a bare clone
and tar it. You will not need to compress the tar.
You can also use split(1) to break up the bundle or tar into smaller
chunks if that helps. cat(1) will happily recombine those chunks.
If git bundle was not available, you can use the copied bare repo as
a --reference for a new clone, then copy the bare's pack file into
that new clone and remove the new clone's objects/info/alternates file.
I've had to use that method to get a clean clone across a small straw
(dialup or wireless) for several large repositories over the years.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
prev parent reply other threads:[~2011-01-10 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 14:28 git fails on large repo clone on intermittent, or intermittently-high-latency, connections Zenaan Harkness
2011-01-05 15:26 ` Jakub Narebski
2011-01-05 17:54 ` Jonathan Nieder
2011-01-05 20:00 ` Jakub Narebski
2011-01-09 20:04 ` James Cloos [this message]
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=m38vyt7shs.fsf@jhcloos.com \
--to=cloos@jhcloos.com \
--cc=git@vger.kernel.org \
--cc=zen@freedbms.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.