> -----Original Message-----
> From: Josef Wolf
> Sent: Friday, September 13, 2013 6:23
> On Thu, Sep 12, 2013 at 08:06:35PM +0000, Pyeron, Jason J CTR
> (US) wrote:
> > Yes, but it is those awfully slow connections (slower that
> the looping
> > issue) which happen to always drop while cloning from our
> office. And
> > the round trip should be mitigated by http-keep-alives.
> [ ... ]
> > But, again if the connection drops, we have already lost the delta
> > advantage. I would think the scenario would go like this:
> > git clone url://blah/blah
> > [fail]
> > cd blah
> > git clone --resume #uses normal methods....
I am using the mythical --resume, where it would fetch packs and indexes.
> > [fail]
> > while ! git clone --resume --HitItWithAStick
> > replace clone with fetch for that use case too
> Last time I checked, cloning could not be resumed:
> If you're on a slow/unreliable link, you've lost.
That is kind of the point. It should be possible.
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
This message is copyright PD Inc, subject to license 20080407P00.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html