From: Philip Oakley <philipoakley@iee.org>
To: Xeno Amess <xenoamess@gmail.com>, git@vger.kernel.org
Subject: Re: Delivery Status Notification (Failure) ... connection lost
Date: Thu, 20 Jun 2019 15:42:36 +0100 [thread overview]
Message-ID: <299a4753-6d93-7114-f00b-4c2a31814e0e@iee.org> (raw)
In-Reply-To: <CAFF4x5LFYQqHnUSzqd1R9NJ=ZVKs3yFqZA=RdrihVx74BtKWMg@mail.gmail.com>
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
prev parent reply other threads:[~2019-06-20 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFF4x5LfJ7qY73JE-=mah5vx9PdeNhc0i0X6kQohPpvDTCd3Sw@mail.gmail.com>
[not found] ` <5cff8197.1c69fb81.4940.6de6.GMR@mx.google.com>
2019-06-11 10:29 ` Delivery Status Notification (Failure) Xeno Amess
2019-06-20 14:42 ` Philip Oakley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=299a4753-6d93-7114-f00b-4c2a31814e0e@iee.org \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=xenoamess@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).