From: Jonathan Tan <jonathantanmy@google.com>
To: jkapil.cs@gmail.com
Cc: git@vger.kernel.org, t.gummerer@gmail.com,
Jonathan Tan <jonathantanmy@google.com>
Subject: Re: New Ft. for Git : Allow resumable cloning of repositories.
Date: Fri, 8 Mar 2019 09:43:14 -0800 [thread overview]
Message-ID: <20190308174314.129611-1-jonathantanmy@google.com> (raw)
In-Reply-To: <CAMknYENWOW0mj6Bn9OooqKg-sZi9bZUO461Gv1F00=phNwLFQQ@mail.gmail.com>
> Objective: Allow pause and resume functionality while cloning repositories.
>
> Below is a rough idea on how this may be achieved.
This is indeed a nice feature to have, and thanks for details of how
this would be accomplished.
> 1) Create a repository_name.json file.
> 2) repository_name.json will be an index file containing list of all
> the files in the repository with default status being "False".
> "False" status of a file signifies that this file is not yet fully
> downloaded.
>
> Something like this:
>
> {
> 'file1.ext' : "False",
> 'file2.ext' : "False",
> 'file3.ext' : "False"
> }
One issue is that when cloning a repository, we do not download many
files - we only download one dynamically generated packfile containing
all the objects we want.
You might be interested in some work I'm doing to offload part of the
packfile response to CDNs:
https://public-inbox.org/git/cover.1550963965.git.jonathantanmy@google.com/
This means that when cloning/fetching, multiple files could be
downloaded, meaning that a scheme like you suggest would be more
worthwhile. (In fact, I allude to such a scheme in the design document
in patch 5.)
next prev parent reply other threads:[~2019-03-08 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 15:43 New Ft. for Git : Allow resumable cloning of repositories Kapil Jain
2019-03-08 17:43 ` Jonathan Tan [this message]
2019-03-10 15:59 ` Kapil Jain
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=20190308174314.129611-1-jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--cc=jkapil.cs@gmail.com \
--cc=t.gummerer@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.
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).