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

Server-side-proposed partial clone configuration (default clone --filter option)

From
Marc Strapetz <marc.strapetz@syntevo.com>
Date
Jun 11, 2021, 16:40 UTC
Message-ID
<f6b3e10e-06b0-fa98-4e34-8a0eeaf45849@syntevo.com>
 From a (GUI) client perspective, it would be quite helpful to propose 
good (partial) clone defaults to the user: whether to do a full clone, 
or skip large blobs, ... this can result in much smaller clones by 
*default* and thus a better user experience.

Such a proposal should most likely be a property of the repository itself, for example stored in a specific ref which can efficiently be fetched using Git, in preparation of the main clone.

Are there any best practices on how to implement that? Or even better, is there any specification on where this meta information should be stored, how it should look like, ...? If not, is anyone interested in this topic? I feel that this is something which not every platform/client should reinvent.

-Marc
Message 1 of 1 in “Server-side-proposed partial clone configuration (default clone --filter option)”
  1. Marc StrapetzJun 11, 2021

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.