mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kapil Jain <>
To:, Thomas Gummerer <>
Subject: New Ft. for Git : Allow resumable cloning of repositories.
Date: Fri, 8 Mar 2019 21:13:36 +0530	[thread overview]
Message-ID: <> (raw)

Objective: Allow pause and resume functionality while cloning repositories.

Below is a rough idea on how this may be achieved.

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

Something like this:

  'file1.ext' : "False",
  'file2.ext' : "False",
  'file3.ext' : "False"

3) As a file finishes downloading, say 'file1.ext' and 'file2.ext'
have finished downloading, their status will change to:

Something like this:

  'file1.ext' : "True",
  'file2.ext' : "True",
  'file3.ext' : "False"

4) Suppose due to some reason, before 'file3.ext' could finish
download; cloning is interrupted.
5) After the interruption the repository_name.json and downloaded
files are preserved.
6) Now, when cloning of the same repository begins next time, files
would be downloaded based on information taken from
repository_name.json file.

Note 1: Doing this for cloning would be the main objective, further
this may be extended for fetching, pulling, and pushing too.

Note 2: Since this is gsoc time, please don't take this to be a
project idea for gsoc, as it was pointed out on irc that this would be
a time intensive functionality.

I want to work on building this functionality.
Please discuss thoughts on this, so as to make a technically sound to-do list.

             reply	other threads:[~2019-03-08 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 15:43 Kapil Jain [this message]
2019-03-08 17:43 ` New Ft. for Git : Allow resumable cloning of repositories Jonathan Tan
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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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

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).