From: Jonathan Tan <jonathantanmy@google.com>
To: Mark Thomas <markbt@efaref.net>, git@vger.kernel.org
Cc: peartben@gmail.com
Subject: Re: [RFC 0/4] Shallow clones with on-demand fetch
Date: Mon, 6 Mar 2017 11:16:23 -0800 [thread overview]
Message-ID: <c8788f30-263b-c96a-239d-940743b96b53@google.com> (raw)
In-Reply-To: <20170304191901.9622-1-markbt@efaref.net>
On 03/04/2017 11:18 AM, Mark Thomas wrote:
> I was inspired a bit by Microsoft's announcement of their Git VFS. I
> saw that people have talked in the past about making git fetch objects
> from remotes as they are needed, and decided to give it a try.
For reference, one such conversation is [1]. (cc-ing Ben Peart also)
> The patch series adds a "--on-demand" option to git clone, which, when
> used in conjunction with the existing shallow clone operations, clones
> the full history of the repository's commits, but only the files that
> would be included in the shallow clone.
>
> When a file that is missing is required, git requests the file on-demand
> from the remote, via a new 'upload-file' service.
A reachability check (of the blob) might be a good idea. The current Git
implementation already supports fetching a blob (perhaps a bug) but has
problems with reachability calculations that I tried to fix in [2], but
found some bugs that weren't easily fixable.
As I said in [2], I think that proper fetching of blobs on demand is a
prerequisite to any sort of missing object tolerance (like your
on-demand clones), so I haven't thought much about the topics in the
rest of your patch set.
[1] <20170113155253.1644-1-benpeart@microsoft.com> (you can search for
emails by Message ID in online archives like
https://public-inbox.org/git if you don't already have them)
[2] <cover.1487984670.git.jonathantanmy@google.com>
next prev parent reply other threads:[~2017-03-06 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 19:18 [RFC 0/4] Shallow clones with on-demand fetch Mark Thomas
2017-03-04 19:18 ` [RFC 1/4] upload-file: Add upload-file command Mark Thomas
2017-03-04 19:18 ` [RFC 2/4] on-demand: Fetch missing files from remote Mark Thomas
2017-03-04 19:19 ` [RFC 3/4] upload-pack: Send all commits if client requests on-demand Mark Thomas
2017-03-04 19:19 ` [RFC 4/4] clone: Request on-demand shallow clones Mark Thomas
2017-03-06 19:16 ` Jonathan Tan [this message]
2017-03-06 20:01 ` [RFC 0/4] Shallow clones with on-demand fetch Stefan Beller
2017-03-06 19:18 ` Junio C Hamano
2017-03-07 9:42 ` Jeff King
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=c8788f30-263b-c96a-239d-940743b96b53@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--cc=markbt@efaref.net \
--cc=peartben@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.
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).