From: Sitaram Chamarty <sitaramc@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Thiago Farina <tfransosi@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: resume downloads
Date: Tue, 12 May 2015 15:24:08 +0530 [thread overview]
Message-ID: <5551CDC0.10101@gmail.com> (raw)
In-Reply-To: <CAPc5daVwxEniz-s-6dcowQkE-bK50wJ4MOCWGkAM=u02BGtN+w@mail.gmail.com>
On 05/11/2015 03:49 AM, Junio C Hamano wrote:
> The current thinking is to model this after the "repo" tool.
> Prepare a reasonably up-to-date bundle file on the server side,
<shameless plug (but not "commercial")>
For people using gitolite, the server side issues of generating a
reasonably up-to-date bundle *and* enabling it for resumable download
using rsync (with the same ssh key used to gain gitolite access), can
all be handled by gitolite.
</shameless plug>
Of course the client side issues still remain; gitolite can't help
there.
> add a protocol capability to advertise the URL to download that
> bundle from upload-pack, and have "git clone" to pay attention to it.
>
> Then, a "git clone" could become:
>
> - If the capability advertises such a prebuilt bundle, spawn "curl"
> or "wget" internally to fetch it. This can be resumed when the
> connection goes down and will grab majority of the data necessary.
>
> - Extract the bundle into temporary area inside .git/refs/ to help
> the next step.
>
> - Internally do a "git fetch" to the original server. Thanks to the
> bundle transfer that has already happened, this step will become
> a small incremental update.
>
> - Then prune away the temporary .git/refs/ refs that were in the
> bundle, as these are not the up-to-date refs that exist on the
> server side.
>
> A few points that need to be considered by whoever is doing this
> are:
>
> - Where to download the bundle, so that after killing "git clone"
> that is still in the bundle-download phase, the next invocation
> of "git clone" can notice and resume the bundle-download;
>
> - What kind of transfer protocols do we want to support? Is http
> and https from CDN sufficient? In other words, what exactly
> should the new capability say to point at the prebuilt bundle?
>
> These (and probably there are several others) are not something
> that "repo" does not have to worry about, but would become
> issues when we try to fold this into "git clone".
>
>
>
> On Sun, May 10, 2015 at 2:55 PM, Thiago Farina <tfransosi@gmail.com> wrote:
>> Hi,
>>
>> Is there links to discussion on this? I mean, is resume downloads a
>> feature that is still being considered?
>>
>> Being able to download huge repos like WebKit, Linux, LibreOffice in
>> small parts seems like a good feature to me.
>>
>> --
>> Thiago Farina
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-05-12 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 21:55 resume downloads Thiago Farina
2015-05-10 22:19 ` Junio C Hamano
2015-05-12 9:54 ` Sitaram Chamarty [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5551CDC0.10101@gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tfransosi@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.
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 NNTP newsgroup(s).