git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
* Broken-point Continuingly-cloning
@ 2020-11-02 11:37 Wenyin Wei
  2020-11-02 21:18 ` Philip Oakley
  0 siblings, 1 reply; 2+ messages in thread
From: Wenyin Wei @ 2020-11-02 11:37 UTC (permalink / raw)
  To: git

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Broken-point Continuingly-cloning
  2020-11-02 11:37 Broken-point Continuingly-cloning Wenyin Wei
@ 2020-11-02 21:18 ` Philip Oakley
  0 siblings, 0 replies; 2+ messages in thread
From: Philip Oakley @ 2020-11-02 21:18 UTC (permalink / raw)
  To: Wenyin Wei, git

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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-11-02 21:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-02 11:37 Broken-point Continuingly-cloning Wenyin Wei
2020-11-02 21:18 ` Philip Oakley

git@vger.kernel.org list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ https://public-inbox.org/git \
		git@vger.kernel.org
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.version-control.git
	nntp://ie5yzdi7fg72h7s4sdcztq5evakq23rdt33mfyfcddc5u3ndnw24ogqd.onion/inbox.comp.version-control.git
	nntp://4uok3hntl7oi7b4uf4rtfwefqeexfzil2w6kgk2jn5z2f764irre7byd.onion/inbox.comp.version-control.git
	nntp://news.gmane.io/gmane.comp.version-control.git
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git