This is absolutely awesome. I barely use Git myself - my use cases have pretty much been https://xkcd.com/1597/ https://xkcd.com/1597/ - but the two main featur

This is absolutely awesome. I barely use Git myself - my use cases have pretty much been https://xkcd.com/1597/ https://xkcd.com/1597/ - but the two main features I have needed to use are --depth=1 (to download just recent files) and "just fetch this one file from this one directory". --depth=1 occasionally breaks repos because of the way Git works. I THINK (don't cite!) that Git stores submodule information in the master repo's history. So when I do a depth=1 clone with something that has submodules, I literally don't receive the metadata about the submodule information. But now the local history I do have is borked, and the only way to really fix it is to rm -rf the destination and start again. But it's typically directories with submodules that also have massive histories. Like ffmpeg, for example. Yay. -- Git doesn't have a "just grab me this one file or directory over there" option. It would probably be possible, but would probably be a massive hack to implement without even considering the internal architecture of Git - I don't know how the packfile format works (been meaning to find out one of these days) but it does seem that it shoves multiple files into the same packfile databases. -- Finally, I am really happy to hear that Fossil-NG is somehow (?!?) going to be able to import Git repositories. I never wanted to learn Git - I've been trucking along like the XKCD above, but somewhere along the way I realized that it just wasn't the superior architecture and was glad I'd never adopted it. At some point I hope to learn Fossil and Mercurial, with Git a begrudging afterthought. I love how Git is referred to not once but twice as a _legacy_ client xD