From: Khalid Masum <khalid.masum.92@gmail.com>
To: git@vger.kernel.org
Subject: [RFC][GSoC Proposal Draft] clone: bundle-uri: make it resumable
Date: Sat, 25 Mar 2023 14:36:58 +0600 [thread overview]
Message-ID: <20e57ea3-3284-a5c8-09a8-5f2159818d57@gmail.com> (raw)
Hello!
This is my draft proposal to implement resumable bundle-uri clone.
I would love to hear your thoughts on this. Also, I think the timeline
section
could be improved amd I need your input on that.
thanks,
-- Khalid Masum
======================================================
GSoC23 Draft Proposal: Resumable cloning with git bundle
======================================================
Overview:
=========
Currently, git clones are not resumable. But there is a workaround using
git bundles, where the user can `wget -c` the bundle, then clone from it.
However this comes with drawbacks that `git clone` does not have. For
example, with git clone we can specify branch, or send authentication
credentials,
which we can not do with `wget` in a simple manner.
However with the new `bundle-uri` we should be able to add this feature.
As suggested by Derrick Stolee <derrickstolee@github.com> here:
https://lore.kernel.org/git/7097d1d6-00a1-2a82-1923-610d41f4053f@github.com/
Where it is suggested that, the randomized temporary download files
could be
renamed with hashed url, enabling the ability to have resumable clone.
Deliverables:
=============
- Ability to resume a cloning process with bundle-uri.
- Testcases for the newly added feature.
- Update on documentation for the newer changes.
Timeline:
=========
Before April 25:
- Familiarize myself with git's codebase and architecture.
- Making small contributions to git.
Before May 25:
- Research and familiarize with git bundle and git object download
process.
- Understanding the core implementation of git bundle.
- Communicate with mentors for further understanding and finding
ways of
implementation.
May 26 - June 20:
- Starting to implement the git bundle-uri resumable feature.
- Refactor the codebase for necessary integration.
- Write some of the test-cases for the created modules.
June 21- July 20:
- Finish implementing the feature.
- Necessary test cases are implemented and reviewed.
- Document the changes.
July 21 - Aug 10:
- Finishing touches, making sure everything is stable.
Aug 11- 27:
- Buffer period for any unexpected events.
- Final report writing.
- Project submission
Contributions
==============
Microproject:
-------------
Modernized test script: t3501
Link:
https://lore.kernel.org/git/20220405150657.19801-1-khalid.masum.92@gmail.com/
Status: Accepted
Other contributions:
--------------------
Patch review:
https://lore.kernel.org/git/pull.1474.git.git.1679233875803.gitgitgadget@gmail.com/
Motivation:
===========
I am captivated by the engineering behind Git and aspire to contribute
regularly to the project, impacting its features. I view GSoC as an
excellent opportunity to jumpstart my contributions and deepen my
understanding of software engineering.
Conclusion:
===========
Implementation of resumable clone is a long wanted feature in git
since 2011. With this contribution I believe we will be able to be
closer to this goal, or at least get a very good workaround on this
feature.
reply other threads:[~2023-03-25 8:38 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=20e57ea3-3284-a5c8-09a8-5f2159818d57@gmail.com \
--to=khalid.masum.92@gmail.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).