3 ms·
This looks like it’s supposed to be more appropriate for very, very big repos. Which current Git doesn’t support and isn’t fundamentally designed to support. S
by avgcorrection 5y ago
This looks like it’s supposed to be more appropriate for very, very big repos. Which current Git doesn’t support and isn’t fundamentally designed to support.
So rather than use Git + Git Annex or something like that (maybe more), you’ll just use this alternative SCM.
(I keep hearing about how Git will eventually support big repos, but it’s still not on the horizon. Big repos with Git still seems to be limited to big corps who have the resources to make something bespoke. Personally I don’t use big repos so I have no skin in this game.)
- kevincox 5y agoBig repos work in Git today if you are able to play the sparse checkout dance. There are definitely more improvements to be made. - Protocol for more efficiently widening sparse checkouts. - Virtual filesystem or other solution for automatically widening sparse checkouts to greatly improve the UX. - Ideally changing sparse checkouts from a repo state to just some form of lazy loading. Otherwise as you touch more files your performance will slowly degrade.