{"thread":{"id":"54552","subject":"Broken-point Continuingly-cloning","startedAt":"2020-11-02T11:37:51Z","lastAt":"2020-11-02T21:18:22Z","messageCount":2,"participants":["Wenyin Wei","Philip Oakley"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"408858","messageId":"CABKv=+456ECj_JgHZwnjPt_3H4odWmuM=3+G0FF+X+0noVcCfg@mail.gmail.com","threadId":"54552","inReplyTo":null,"subject":"Broken-point Continuingly-cloning","fromName":"Wenyin Wei","fromEmail":"wenyin.wei.ww@gmail.com","sentAt":"2020-11-02T11:37:37Z","receivedAt":"2020-11-02T11:37:51Z","isPatch":false,"sender":{"key":"wenyin.wei.ww@gmail.com","avatar":null},"body":"Dear Git Community,\n\nConsider the number of large repositories using Git has increased\nthese years dramatically, is it possible for Git to make a\ndiscontinuous clone way? The required continuity for a git clone has\nbeen hard for large repos, and developers have strived by the somewhat\nugly way, `git fetch –depth=<increasing n>`.\n\n1. https://stackoverflow.com/questions/38618885/error-rpc-failed-curl-transfer-closed-with-outstanding-read-data-remaining\n2. https://stackoverflow.com/questions/60878838/git-rpc-failed-curl-18-transfer-closed-with-outstanding-read-data-remaining\n\nIt would be appreciated for many developers to see that git could\nsupport something like broken-point continuingly-cloning. I am not\nsure whether the `git clone git@......` way supports this\nfunctionality, but even so, some mirror hubs in China, to accelerate\ncloning, only support the `https` way and then become anxious while\ncloning. Anticipate your comments and reply.\n\nBest Wishes,\nWenyin Wei\n"},{"id":"408929","messageId":"5adca37d-20df-ba9d-fd26-097c2cbdead2@iee.email","threadId":"54552","inReplyTo":"CABKv=+456ECj_JgHZwnjPt_3H4odWmuM=3+G0FF+X+0noVcCfg@mail.gmail.com","subject":"Re: Broken-point Continuingly-cloning","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2020-11-02T21:18:18Z","receivedAt":"2020-11-02T21:18:22Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"On 02/11/2020 11:37, Wenyin Wei wrote:\n> Dear Git Community,\n>\n> Consider the number of large repositories using Git has increased\n> these years dramatically, is it possible for Git to make a\n> discontinuous clone way? The required continuity for a git clone has\n> been hard for large repos, and developers have strived by the somewhat\n> ugly way, `git fetch –depth=<increasing n>`.\n>\n> 1. https://stackoverflow.com/questions/38618885/error-rpc-failed-curl-transfer-closed-with-outstanding-read-data-remaining\n> 2. https://stackoverflow.com/questions/60878838/git-rpc-failed-curl-18-transfer-closed-with-outstanding-read-data-remaining\n>\n> It would be appreciated for many developers to see that git could\n> support something like broken-point continuingly-cloning. I am not\n> sure whether the `git clone git@......` way supports this\n> functionality, but even so, some mirror hubs in China, to accelerate\n> cloning, only support the `https` way and then become anxious while\n> cloning. Anticipate your comments and reply.\n>\n> Best Wishes,\n> Wenyin Wei\nDo have a look at the Partial Clone methods which IIUC have been\ndeveloped to align with the problem of large repos (such as Windows).\nThis filters the download to just those that have been selected as 'needed.\n\nThere was also, separately, some patches to IIRC keep alive connections\nfor places with slow internet connections.\n\nThe list archive is at https://lore.kernel.org/git/ and is relatively\neasy to search.\n\n[e.g. keepalive]\nhttps://lore.kernel.org/git/20160715104347.GL19271@sigill.intra.peff.net/\n"}]}