git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Wenyin Wei <wenyin.wei.ww@gmail.com>
To: git@vger.kernel.org
Subject: Broken-point Continuingly-cloning
Date: Mon, 2 Nov 2020 19:37:37 +0800	[thread overview]
Message-ID: <CABKv=+456ECj_JgHZwnjPt_3H4odWmuM=3+G0FF+X+0noVcCfg@mail.gmail.com> (raw)

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

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 11:37 Wenyin Wei [this message]
2020-11-02 21:18 ` Broken-point Continuingly-cloning Philip Oakley

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='CABKv=+456ECj_JgHZwnjPt_3H4odWmuM=3+G0FF+X+0noVcCfg@mail.gmail.com' \
    --to=wenyin.wei.ww@gmail.com \
    --cc=git@vger.kernel.org \
    /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).