From: Derrick Stolee <stolee@gmail.com>
To: git@vger.kernel.org
Subject: Partial Clone: Commands that could be problematic
Date: Wed, 7 Mar 2018 08:57:07 -0500 [thread overview]
Message-ID: <04927620-c5ea-ee70-2104-4a5a7a994e33@gmail.com> (raw)
We discussed partial clone today during the contributor's summit. There
were some concerns about some commands that would cause over-hydration
of blobs that need server requests to resolve.
GVFS blocks "fsck", "gc", "prune", "repack", "submodule", and "worktree"
[1]. I promised I would include this list. There are a few limitations
on the arguments of the other commands, as seen in that code. These
commands that are blocked are already handled in partial clone with the
"promisor" pattern. The "worktree" limitation is only due to the
file-system virtualization layer of GVFS.
We discussed commands like "git grep" that sometimes look at the working
directory and sometimes crawls trees. That is a command that should be
considered for batching object downloads, limiting the command to
"hydrated" blobs, or limiting to a sparse checkout.
Thanks,
-Stolee
[1]
https://github.com/Microsoft/GVFS/blob/2db0c030eb257beebf8e17f1c2ce72ffb166f533/GVFS/GVFS.Hooks/Program.cs#L120-L137
reply other threads:[~2018-03-07 13:57 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04927620-c5ea-ee70-2104-4a5a7a994e33@gmail.com \
--to=stolee@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.
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).