git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Delivery Status Notification (Failure)

From
XAXeno Amess <xenoamess@gmail.com>
Date
Jun 11, 2019, 10:29 UTC
Message-ID
<CAFF4x5LFYQqHnUSzqd1R9NJ=ZVKs3yFqZA=RdrihVx74BtKWMg@mail.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?

Next: Philip Oakley
Message 1 of 2 in “Re: Delivery Status Notification (Failure)”
  1. Xeno AmessJun 11, 2019
  2. Philip OakleyJun 20, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.