From: Jonathan Nieder <jrnieder@gmail.com>
To: netroby <hufeng1987@gmail.com>
Cc: Git Mail List <git@vger.kernel.org>,
Tomas Carnecky <tom@dbservice.com>, Jeff King <peff@peff.net>
Subject: Re: New Feature wanted: Is it possible to let git clone continue last break point?
Date: Mon, 31 Oct 2011 04:07:18 -0500 [thread overview]
Message-ID: <20111031090717.GA24978@elie.hsd1.il.comcast.net> (raw)
In-Reply-To: <CAEZo+gcj5q2UYnak1+1UG7pPzoeaUr=QLsiCiNXbC_n+JQbKQQ@mail.gmail.com>
Hi,
netroby wrote:
> 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 .
You might find [1] useful as a stopgap (thanks, Tomas!).
Something like Jeff's "priming the well with a server-specified
bundle" proposal[2] might be a good way to make the same trick
transparent to clients in the future.
Even with that, later fetches, which grab a pack generated on the fly
to only contain the objects not already fetched, are generally not
resumable. Overcoming that would presumably require larger protocol
changes, and I don't know of anyone working on it. (My workaround
when in a setup where this mattered was to use the old-fashioned
"dumb" http protocol. It worked fine.)
Hope that helps,
Jonathan
[1] http://thread.gmane.org/gmane.comp.version-control.git/181380
[2] http://thread.gmane.org/gmane.comp.version-control.git/164569/focus=164701
http://thread.gmane.org/gmane.comp.version-control.git/168906/focus=168912
next prev parent reply other threads:[~2011-10-31 9:07 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 [this message]
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
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=20111031090717.GA24978@elie.hsd1.il.comcast.net \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hufeng1987@gmail.com \
--cc=peff@peff.net \
--cc=tom@dbservice.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).