I wonder what's the problem with implementing clone resume after an error in Git.
🇳🇱
@a1batross Id imagine the big problem being that it has no way of knowing if the repo changed since the first clone started and failed. Normally the server would handle that by temporarily cacheing a complete copy of the repo whent he clone starts but it discards that cache the second the connection drops. someone may have changed the repo in the time it akes you to resume.
@freemo yeah I think over HTTP protocol (which is the reason why I can't fetch some repos) it's impossible to keep up with the changes.
Follow
@a1batross In theory its possible even under ssh, the problem is it would require a significant change to the standard around a clone
