From: Philip Oakley <philipoakley@iee.email>
To: "Eric Wong" <e@80x24.org>, "Michal Suchánek" <msuchanek@suse.de>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, m <mahg361@gmail.com>,
git@vger.kernel.org, Derrick Stolee <derrickstolee@github.com>
Subject: Re: [feature request] resume capability for users in enemies of Internet countries
Date: Fri, 7 Oct 2022 11:03:37 +0100 [thread overview]
Message-ID: <8e11ecf0-735a-a104-a3d1-8324fbd76862@iee.email> (raw)
In-Reply-To: <20221007072606.M704368@dcvr>
On 07/10/2022 08:26, Eric Wong wrote:
> Michal Suchánek <msuchanek@suse.de> wrote:
>> On Fri, Oct 07, 2022 at 08:44:09AM +0700, Bagas Sanjaya wrote:
>>> On 10/7/22 01:01, m wrote:
>>>> In my country government make connections unstable on purpose. Please add resume capability for commands like git clone
>>>>
>>> Bandwidth issue?
>>>
>> Bandwidth is one thing but the other thing is that git network
>> operations require that the whole operation succeeds in one go.
>>
>> If your connectivity is bad to the point that the TCP connection breaks
>> you have downloaded a bunch of data that is AFAIK just thrown away when
>> you retry.
>>
>> It is difficult to know if that data would be useful in the future, and
>> you cannot meaningfully 'resume' because the remote state might have
>> changed in the meantine as well.
>>
>> Further, this whole fetch operation is using a heuristic to fetch some
>> data in the hope that it will be enough to reconstruct the history that
>> is requested, and this has been wrong in some cases, too. Not very
>> precise and reproducible hence hard to 'resume' as well.
>>
>> Let's say that the git networking has been developed at and tuned for
>> the 'first world' Internet, and may be problematic to use in net-wise
>> backwater areas. And it would require non-trivial effort to change.
> Increased adoption of bundles would help, since `wget -c' and such
> would work nicely, but that puts the burden on hosts for extra storage.
>
> Perhaps GIT_SMART_HTTP=0 and having dumb clones not throwaway
> incomplete xfers would be more transparent to hosters, but dumb
> HTTP tends to be slow even on good connections.
There is work going on by Stollee (cc'd) on Bundle-URIs that look to
split up repository serving into bite sized chunk, so may be worth
looking at.
https://lore.kernel.org/git/pull.1248.v4.git.1660050761.gitgitgadget@gmail.com/
: [PATCH v4 0/2] bundle URIs: design doc
Also discussed at the recent Contributor's Summit
https://lore.kernel.org/git/YzXvwv%2FzK5AjhVvV@nand.local/ : [TOPIC 1/8]
Bundle URIs
--
Philip
next prev parent reply other threads:[~2022-10-07 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 18:01 [feature request] resume capability for users in enemies of Internet countries m
2022-10-07 1:44 ` Bagas Sanjaya
2022-10-07 7:14 ` Michal Suchánek
2022-10-07 7:26 ` Eric Wong
2022-10-07 10:03 ` Philip Oakley [this message]
2022-10-07 14:24 ` Derrick Stolee
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=8e11ecf0-735a-a104-a3d1-8324fbd76862@iee.email \
--to=philipoakley@iee.email \
--cc=bagasdotme@gmail.com \
--cc=derrickstolee@github.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=mahg361@gmail.com \
--cc=msuchanek@suse.de \
/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).