git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Partial Clone: Commands that could be problematic

From
Derrick Stolee <stolee@gmail.com>
Date
Mar 7, 2018, 13:57 UTC
Message-ID
<04927620-c5ea-ee70-2104-4a5a7a994e33@gmail.com>

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

Message 1 of 1 in “Partial Clone: Commands that could be problematic”
  1. Derrick StoleeMar 7, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.