Gitifying I2P: How to make Git clone resumable
1–5 of 5 posts
Re: Gitifying I2P: How to make Git clone resumable
#2The author's workaround before their solution is quite clever. "
Gitifying I2P: How to make git clone resumable Have you ever cloned a git repository on a bad internet connection? I have, it don't work. When I lived in the Philippines for a year and a half, I had to clone repositories to a server of mine in Norway, for then sharing the repo via torrent so I could download it to my laptop in the Philippines. "
Re: Gitifying I2P: How to make Git clone resumable
#3I've never put much thought into how git clones aren't resumable. The author's workaround before their solution is quite clever. " Gitifying I2P: How to make git clone resumable Have you ever cloned a git repository on a bad internet connection? I have, it don't work. When I lived in the Philippines for a year and a half, I had to clone repositories to a server of mine in Norway, for then sharing the repo via torrent…
Re: Gitifying I2P: How to make Git clone resumable
#4Re: Gitifying I2P: How to make Git clone resumable
#5I've never put much thought into how git clones aren't resumable. The author's workaround before their solution is quite clever. " Gitifying I2P: How to make git clone resumable Have you ever cloned a git repository on a bad internet connection? I have, it don't work. When I lived in the Philippines for a year and a half, I had to clone repositories to a server of mine in Norway, for then sharing the repo via torrent…
In cases like that, I find it far simpler to download an archive of the remote repo. A competent download manager supports resuming, and if you sha1sum the archive you can verify integrity.
for example you can resume a download if you use their own http client named eepget IIRC, but it won't work if you use a standard http client meant for plain internet like wget/curl