On Fri, 2 Nov 2012 13:58:44 -0700 (PDT)
Thomas Ferris Nicolaisen <tfn...@gmail.com> wrote:
> > Still, for some particularly long running operations it would be
> > good to know if there is a way to "resume" something in process
> > rather than simply discovering the anomaly, wiping the anomaly
> > completely and starting from the beginning again.
> Just repeat the operation with the same command you used the first
> time, unless it was git clone, in which case you can resume it with
> git fetch.
Continuing the "resumable clone" thread, a one nifty feature of
gitolite has been somewhat recently discussed on the main Git list .
Basically, gitolite can be configured to update a "Git bundle" (see the
git-bundle manual) which is then can be made downloadable via rsync or
HTTP protocols and then it can be downloaded using an rsync client of a
HTTP client which supports resuming. Using this technique can make the
"download everything" and "make a repo out of the downloaded stuff"
steps distinct, and the first step can be carried out using any number
of attempts. The downsides are obvious:
1) This requires special setup on the server side.
2) It's unclear what happens if someone manages to update a repository
while someone is downloading its bundle, or the update happens
between the adjacent download attempts.