From: Michael Schubert <mschub@elegosoft.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: netroby <hufeng1987@gmail.com>, Git Mail List <git@vger.kernel.org>
Subject: Re: New Feature wanted: Is it possible to let git clone continue last break point?
Date: Mon, 31 Oct 2011 13:49:05 +0100 [thread overview]
Message-ID: <4EAE9941.2080609@elegosoft.com> (raw)
In-Reply-To: <m3obwx4j7s.fsf@localhost.localdomain>
On 10/31/2011 10:14 AM, Jakub Narebski wrote:
> netroby <hufeng1987@gmail.com> writes:
>
>> Is it possible to let git clone continue last break point.
>> when we git clone very large project from the web, we may face some
>> interupt, then we must clone it from zero .
>>
>> it is bad feeling for low connection speed users.
>>
>> please help us out.
>>
>> we need git clone continue last break point
>
> Resuming "git clone" is not currently possible in Git, and it would be
> difficult to add such feature to Git; there were several attempts and
> neither succeeded.
>
> What you can do is generate a starter bundle out of your repository
> (using "git bundle"), and serve this file via HTTP / FTP / BitTorrent,
> i.e. some resumable transport. Then you "git clone <bundle file>",
> fix up configuration, and fetch the rest since bundle creation.
There's also a "git bundler service":
http://comments.gmane.org/gmane.comp.version-control.git/181380
prev parent reply other threads:[~2011-10-31 12:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEZo+gfKVY-YgMjd=bEYzRV4-460kqDik-yVcQ9Xs=DoCZOMDg@mail.gmail.com>
2011-10-31 2:28 ` New Feature wanted: Is it possible to let git clone continue last break point? netroby
2011-10-31 4:00 ` Tay Ray Chuan
2011-10-31 9:07 ` Jonathan Nieder
2011-10-31 9:16 ` netroby
2011-11-02 22:06 ` Jeff King
2011-11-02 22:41 ` Junio C Hamano
2011-11-02 23:27 ` Jeff King
2011-11-03 0:06 ` Shawn Pearce
2011-11-03 2:42 ` Jeff King
2011-11-03 4:19 ` Shawn Pearce
2011-11-04 8:56 ` Clemens Buchacher
2011-11-04 9:35 ` Johannes Sixt
2011-11-04 14:22 ` Shawn Pearce
2011-11-04 15:55 ` Jakub Narebski
2011-11-04 16:05 ` Nguyen Thai Ngoc Duy
2011-11-05 10:00 ` Clemens Buchacher
2011-10-31 9:14 ` Jakub Narebski
2011-10-31 12:49 ` Michael Schubert [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=4EAE9941.2080609@elegosoft.com \
--to=mschub@elegosoft.com \
--cc=git@vger.kernel.org \
--cc=hufeng1987@gmail.com \
--cc=jnareb@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).