git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Zenaan Harkness <zen@freedbms.net>, git@vger.kernel.org
Subject: Re: git fails on large repo clone on intermittent, or intermittently-high-latency, connections
Date: Wed, 5 Jan 2011 11:54:12 -0600	[thread overview]
Message-ID: <20110105175412.GA21863@burratino> (raw)
In-Reply-To: <m3tyhnbcf7.fsf@localhost.localdomain>

Jakub Narebski wrote:
> Zenaan Harkness <zen@freedbms.net> writes:

>> How hard would it be to add a wget-like mode to git, for the initial
>> repo download?
>
> Very hard; tthough "resumable clone" was often requested (25%
> responders in "Git User's Survey 2010", see [1]), and there was even
> some discussion about possible implementation, it was not implemented
> yet, even as proof of concept.
>
> The trouble is that packfile is *generated for a client*, and
> bit-for-bit representation of said pack can vary (e.g. if
> multithreaded packing is enabled; usually a good idea).

That said, one possible partial solution would be to automate
generation of a seed bundle for huge repositories (with a script or
a special parameter to "git gc", maybe) and to document serving such a
seed bundle over HTTP as part of the standard setup.  If this could be
made simple enough that e.g. all large repos on repo.or.cz had such a
seed bundle then I would call it a success. :)

  reply	other threads:[~2011-01-05 17:54 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 [this message]
2011-01-05 20:00     ` Jakub Narebski
2011-01-09 20:04 ` James Cloos

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=20110105175412.GA21863@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --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 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).