git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Son Luong Ngoc <sluongng@gmail.com>
To: Benson Muite <benson_muite@emailplus.org>
Cc: git <git@vger.kernel.org>, Jonathan Tan <jonathantanmy@google.com>
Subject: Re: Caching Git Pull
Date: Mon, 14 Sep 2020 10:39:00 +0200	[thread overview]
Message-ID: <90AE4B78-36E8-40B6-9D7C-E198E3004941@gmail.com> (raw)
In-Reply-To: <70DB3786-CB8E-4D82-9774-439AB2A79A8D@gmail.com>

Note: resend with plain-text format

Hi Benson,

> On Sep 14, 2020, at 07:27, Benson Muite <benson_muite@emailplus.org> wrote:
> 
> Hi,
> 
> Is there some way I can add functionality for caching git pull to allow continuation of a partially complete pull from a git repository to a local machine. 

I believe there has been some recent works toward this direction with Packfile Uri feature [1] [2] where a packfile could be uploaded to
CDN and then advertised by the hosting remote so that clients who enabled the feature can download the big part of the clone
via CDN instead.

[1]: https://github.com/git/git/blob/master/Documentation/technical/packfile-uri.txt
[2]: https://public-inbox.org/git/cover.1591821067.git.jonathantanmy@google.com/

However I don't think any major Git hosting provider (Github, Bitbucket, Gitlab etc...) have started using this feature.

> As an example the command wget -c allows continuation of a partially complete download. This would be very helpful for large commits which fail with:
> 
> fatal: the remote end hung up unexpectedly
> fatal: early EOF
> 
> Regards,
> Benson

I will cc Jonathan Tan(author) to discuss more regarding path toward resumable git clone.

Cheers,
Son Luong.

      parent reply	other threads:[~2020-09-14  8:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  5:27 Caching Git Pull Benson Muite
     [not found] ` <70DB3786-CB8E-4D82-9774-439AB2A79A8D@gmail.com>
2020-09-14  8:39   ` Son Luong Ngoc [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=90AE4B78-36E8-40B6-9D7C-E198E3004941@gmail.com \
    --to=sluongng@gmail.com \
    --cc=benson_muite@emailplus.org \
    --cc=git@vger.kernel.org \
    --cc=jonathantanmy@google.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).