* Server-side-proposed partial clone configuration (default clone --filter option)
@ 2021-06-11 16:40 Marc Strapetz
0 siblings, 0 replies; only message in thread
From: Marc Strapetz @ 2021-06-11 16:40 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-06-11 17:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-11 16:40 Server-side-proposed partial clone configuration (default clone --filter option) Marc Strapetz
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).