# Re: Delivery Status Notification (Failure) 2 messages from 2019-06-11 to 2019-06-20. Participants: Xeno Amess, Philip Oakley. Thread: https://gitlist.dev/t/51287 ## Xeno Amess, 2019-06-11 10:29 Subject: Re: Delivery Status Notification (Failure) Message-ID: URL: https://gitlist.dev/e/CAFF4x5LFYQqHnUSzqd1R9NJ%3DZVKs3yFqZA%3DRdrihVx74BtKWMg%40mail.gmail.com In-Reply-To: <5cff8197.1c69fb81.4940.6de6.GMR@mx.google.com> ``` Not all people can afford stable network connection... I'm now suffered from connection lost and have to restart the clone/push fully. It's OK when dealing with a project of several MB size, but when I try to clone a 2GB sized repo I never succeed. So I wonder, if there should be some way to resume from break-point for git? For example what if we support something like Content-Range in http, and make the download be split into smaller files, then make some way to auto-resume if some file block failed hash-check? ``` ## Philip Oakley, 2019-06-20 14:42 Subject: Re: Delivery Status Notification (Failure) ... connection lost Message-ID: <299a4753-6d93-7114-f00b-4c2a31814e0e@iee.org> URL: https://gitlist.dev/e/299a4753-6d93-7114-f00b-4c2a31814e0e%40iee.org In-Reply-To: ``` On 11/06/2019 11:29, Xeno Amess wrote: > Not all people can afford stable network connection... > I'm now suffered from connection lost and have to restart the clone/push fully. > It's OK when dealing with a project of several MB size, but when I try > to clone a 2GB sized repo I never succeed. > So I wonder, if there should be some way to resume from break-point for git? > For example what if we support something like Content-Range in http, > and make the download be split into smaller files, then make some way > to auto-resume if some file block failed hash-check? Is this on a Windows machine using Git for Windows, or a Linux machine, or even 'Windows Subsystem for Linux (WSL)" on windows? If it is Windows then you may have hit the "sizeof(long)=32bit" limit. If it is Linux then maybe adjust your refspec to limit the size of each fetch or push. There has also been a recent change discussed on list that added a config variable for some sort of rate limit limit but haven't looked back at the mail archive to try to remember details - try searching the https://public-inbox.org/git/ Philip ```