From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Koosha Khajehmoogahi <koosha.khajeh@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: [GSoC idea] Resumable clone
Date: Tue, 3 Mar 2015 08:02:59 +0700 [thread overview]
Message-ID: <CACsJy8Cue+pxPbddkv1_yMD-SLFO4PjKgdCVX0V7YCn_kUArcQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqoaob7yi8.fsf@gitster.dls.corp.google.com>
On Tue, Mar 3, 2015 at 6:47 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Koosha Khajehmoogahi <koosha.khajeh@gmail.com> writes:
>
>> Among GSoC 2011 ideas of git [1], it was proposed that a GSoC project
>> could be implementing resumable clone for git. AFAIK, this feature is
>> still missing in git but could be a great idea to be implemented. Does
>> that sound OK to the community?
>>
>> [1]: https://git.wiki.kernel.org/index.php/SoC2011Ideas#Resumable_clone
>
> Depends on how it will be implemented, I guess.
I still want to pursue stable pack approach [1]. It's not a good fit
for clone case (cached bundles would be much better). On the other
hand it does not need special support like cached bundles and can work
with upload-pack-v1. It might fit in gsoc scope. I guess whether it
may have a chance to get merged after gsoc is the deciding factor.
> I highly suspect that it would not fly well if it is added as a part
> of the current protocol, as people are actively discussing how to
> revamp it. And I have a feeling that the v2 protocol would not
> ready for a student to build upon by this summer.
[1] http://thread.gmane.org/gmane.comp.version-control.git/184490/focus=184705
Though what I had in mind (and patches) does not need on-disk caching at all.
--
Duy
prev parent reply other threads:[~2015-03-03 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 23:33 [GSoC idea] Resumable clone Koosha Khajehmoogahi
2015-03-02 23:47 ` Junio C Hamano
2015-03-03 1:02 ` Duy Nguyen [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=CACsJy8Cue+pxPbddkv1_yMD-SLFO4PjKgdCVX0V7YCn_kUArcQ@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=koosha.khajeh@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).