git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: Wenyin Wei <wenyin.wei.ww@gmail.com>, git@vger.kernel.org
Subject: Re: Broken-point Continuingly-cloning
Date: Mon, 2 Nov 2020 21:18:18 +0000	[thread overview]
Message-ID: <5adca37d-20df-ba9d-fd26-097c2cbdead2@iee.email> (raw)
In-Reply-To: <CABKv=+456ECj_JgHZwnjPt_3H4odWmuM=3+G0FF+X+0noVcCfg@mail.gmail.com>

On 02/11/2020 11:37, Wenyin Wei wrote:
> 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
Do have a look at the Partial Clone methods which IIUC have been
developed to align with the problem of large repos (such as Windows).
This filters the download to just those that have been selected as 'needed.

There was also, separately, some patches to IIRC keep alive connections
for places with slow internet connections.

The list archive is at https://lore.kernel.org/git/ and is relatively
easy to search.

[e.g. keepalive]
https://lore.kernel.org/git/20160715104347.GL19271@sigill.intra.peff.net/

      reply	other threads:[~2020-11-02 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 11:37 Broken-point Continuingly-cloning Wenyin Wei
2020-11-02 21:18 ` 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=5adca37d-20df-ba9d-fd26-097c2cbdead2@iee.email \
    --to=philipoakley@iee.email \
    --cc=git@vger.kernel.org \
    --cc=wenyin.wei.ww@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).