From: Stefan Beller <sbeller@google.com>
To: Josh Triplett <josh@joshtriplett.org>, Duy Nguyen <pclouds@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
sarah@thesharps.us, viro@zeniv.linux.org.uk
Subject: Re: Resumable git clone?
Date: Tue, 1 Mar 2016 17:40:28 -0800 [thread overview]
Message-ID: <CAGZ79kYjuaOiTCC-NnZDQs=XGbgXWhJe7gk576jod4QnV57eEg@mail.gmail.com> (raw)
In-Reply-To: <20160302012922.GA17114@jtriplet-mobl2.jf.intel.com>
+ Duy, who tried resumable clone a few days/weeks ago
On Tue, Mar 1, 2016 at 5:30 PM, Josh Triplett <josh@joshtriplett.org> wrote:
> If you clone a repository, and the connection drops, the next attempt
> will have to start from scratch. This can add significant time and
> expense if you're on a low-bandwidth or metered connection trying to
> clone something like Linux.
>
> Would it be possible to make git clone resumable after a partial clone?
> (And, ideally, to make that the default?)
>
> In a discussion elsewhere, Al Viro suggested taking the partial pack
> received so far,
ok,
> repairing any truncation,
So throwing away half finished stuff while keeping the front load?
> indexing the objects it
> contains, and then re-running clone and not having to fetch those
> objects.
The pack is not deterministic for a given repository. When creating
the pack, you may encounter races between threads, such that the order
in a pack differs.
> This may also require extending receive-pack's protocol for
> determining objects the recipient already has, as the partial pack may
> not have a consistent set of reachable objects.
>
> Before starting down the path of developing patches for this, does the
> approach seem potentially reasonable?
I think that sounds reasonable on a high level, but I'd expect it blows up
in complexity as in the receive-pack's protocol or in the code for having
to handle partial stuff.
Thanks,
Stefan
>
> - Josh Triplett
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-03-02 1:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 1:30 Resumable git clone? Josh Triplett
2016-03-02 1:40 ` Stefan Beller [this message]
2016-03-02 2:30 ` Al Viro
2016-03-02 6:31 ` Junio C Hamano
2016-03-02 7:37 ` Duy Nguyen
2016-03-02 7:44 ` Duy Nguyen
2016-03-02 7:54 ` Josh Triplett
2016-03-02 8:31 ` Junio C Hamano
2016-03-02 9:28 ` Duy Nguyen
2016-03-02 16:41 ` Josh Triplett
2016-03-02 8:13 ` Josh Triplett
2016-03-02 8:22 ` Duy Nguyen
2016-03-02 8:32 ` Jeff King
2016-03-02 10:47 ` Bhavik Bavishi
2016-03-02 16:40 ` Josh Triplett
2016-03-02 8:14 ` Duy Nguyen
2016-03-02 1:45 ` Duy Nguyen
2016-03-02 8:41 ` Junio C Hamano
2016-03-02 15:51 ` Konstantin Ryabitsev
2016-03-02 16:49 ` Josh Triplett
2016-03-02 17:57 ` Junio C Hamano
2016-03-24 8:00 ` Philip Oakley
2016-03-24 15:53 ` Junio C Hamano
2016-03-24 21:08 ` Philip Oakley
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='CAGZ79kYjuaOiTCC-NnZDQs=XGbgXWhJe7gk576jod4QnV57eEg@mail.gmail.com' \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=josh@joshtriplett.org \
--cc=pclouds@gmail.com \
--cc=sarah@thesharps.us \
--cc=viro@zeniv.linux.org.uk \
/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).