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

Broken-point Continuingly-cloning

From
WWWenyin Wei <wenyin.wei.ww@gmail.com>
Date
Nov 2, 2020, 11:37 UTC
Message-ID
<CABKv=+456ECj_JgHZwnjPt_3H4odWmuM=3+G0FF+X+0noVcCfg@mail.gmail.com>
Dear Git Community,

Consider the number of large repositories using Git has increased these years dramatically, is it possible for Git to make a discontinuous clone way? The required continuity for a git clone has been hard for large repos, and developers have strived by the somewhat ugly way, `git fetch –depth=<increasing n>`.

1. https://stackoverflow.com/questions/38618885/error-rpc-failed-curl-transfer-closed-with-outstanding-read-data-remaining
2. https://stackoverflow.com/questions/60878838/git-rpc-failed-curl-18-transfer-closed-with-outstanding-read-data-remaining

It would be appreciated for many developers to see that git could support something like broken-point continuingly-cloning. I am not sure whether the `git clone git@......` way supports this functionality, but even so, some mirror hubs in China, to accelerate cloning, only support the `https` way and then become anxious while cloning. Anticipate your comments and reply.

Best Wishes, Wenyin Wei

Next: Philip Oakley
Message 1 of 2 in “Broken-point Continuingly-cloning”
  1. Wenyin WeiNov 2, 2020
  2. Philip OakleyNov 2, 2020

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.