git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Varun Garg <varun.10@live.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: [GSoC][Project Idea] Multipart and resumable download while using git clone or pull
Date: Tue, 13 Mar 2018 18:01:55 +0000	[thread overview]
Message-ID: <DM5PR1901MB2167AABED6918A8DAB6E7027F2D20@DM5PR1901MB2167.namprd19.prod.outlook.com> (raw)

Hi,

My name is Varun Garg and am a student in Software Engineering. During 2017 I participated in GSoC at Eclipse Foundation [1] and still contribute occasionally [2]. I have also submitted a micro project here last year[3].

I would like to add functionality of "Multipart and resumable download while using git clone or pull" in git.

Motivation:
The motivation behind this idea came to me when I was downloading linux kernel. Even with shallow clone (--depth=1), the number of objects was too large. Many times we need access to older commits. It is also difficult to update shallow cloned repos [4]. And ssh option is not available behind many firewalls.

Downloading objects incrementally is too slow and we can speed this process by downloading them in parallel (multi part) and adding a resume option will also be lifesaver.

I am looking forward to take this project.

[1] https://summerofcode.withgoogle.com/archive/2017/projects/5762172684599296/
[2] https://github.com/eclipse/omr/pulls?q=author%3AVarun-garg
[3] https://public-inbox.org/git/CY1PR19MB01289DCA6C08CDC9F07C6D7DF2340@CY1PR19MB0128.namprd19.prod.outlook.com/
[4] https://stackoverflow.com/questions/41075972/how-to-update-a-git-shallow-clone

With Best Regards,
Varun Garg 

                 reply	other threads:[~2018-03-13 18:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DM5PR1901MB2167AABED6918A8DAB6E7027F2D20@DM5PR1901MB2167.namprd19.prod.outlook.com \
    --to=varun.10@live.com \
    --cc=git@vger.kernel.org \
    /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).