News for hackers. Stuff that matters.
Re:A Git story: Not so fun this time by cryptonector on Tuesday July 02, 2024 @12:03PM (#40857952)
You say this, but Git has made great strides in scaling to huge repositories in recent years. You can currently do the "checkout just a subtree of the monorepo" just fine, and you can use shallow clones to approximate a centralized system (and most importantly to use less local storage).

> If you had such a system, getting people off git wouldn't be the issue - offer git compatibility and [...]

Git is already doing exactly that.

Re:A Git story: Not so fun this time by vlovich123 on Wednesday July 03, 2024 @02:03PM (#40868491)
Git itself isn’t though, not in any real way that matters. Having to know all the sub trees to clone in a mono repo is a usability nonstarter. You need a pseudo filesystem that knows how to pull files on access. And one ideally integrated with the build system to offset the cost of doing remote operations on demand and improve parallelism. Facebook is open sourcing a lot of their work but it’s based on mercurial. Microsoft is bought into git but afaik hasn’t open sourced their supporting git tooling that makes this feasible.

TLDR: the problem is more complex and pretending like “you can checkout a subtree” solves the problem is missing the proverbial forest for the (sub)tree

Re:A Git story: Not so fun this time by neerajsi on Wednesday July 03, 2024 @04:03PM (#40869514)
Microsoft's vfs for git is open source. So is scalar. These are the two main approaches used at Microsoft for large repos. Unfortunately the technically superior vfs approach was a nonstarter on macOS.
Re:A Git story: Not so fun this time by fragmede on Wednesday July 03, 2024 @02:19PM (#40868634)
> "checkout just a subtree of the monorepo"

How do I check out, eg https://github.com/neovim/neovim/tree/master/scripts into a directory and work with it as if it was a repo unto itself?

Re:A Git story: Not so fun this time by nolist_policy on Wednesday July 03, 2024 @04:22PM (#40869629)
You can't (since commits are snapshots of the repo root). You can have this approximation however:

    git clone --filter=blob:none --sparse https://github.com/neovim/neovim
    cd neovim
    git sparse-checkout add scripts
Unfortunately, GitHub does not support --filter=sparse:oid=master:scripts, so blobs will be fetched on demand as you use the repo.