4 ms·
Why do you think it should be within the scope of git?
by cerved 5y ago
Why do you think it should be within the scope of git?
- IshKebab 5y agoBecause it's something that lots of people want to use Git for, and because it would work better if it were a core part of Git.
- swiley 5y agoMaybe I want to use vim as an interactive WYSIWYG modeling program but that doesn't mean it's in the scope of the project. LFS belongs in your build scripts, the model the git extension use doesn't even match the git VCS model.
- IshKebab 5y agoVersion control of large files is clearly a reasonable thing for a version control system to do. I think if you introspect you'll see you are defending a flaw in something you like with spurious technical objections because you don't want to admit it isn't perfect. That's understandable. Happens a lot.
- swiley 5y agoI didn't say versioning large files isn't a reasonable thing to do, I said it doesn't make sense in git. How is it supposed to work? The LFS way where you're storing a pointer to an external http resource? Just put a script in your repo to fetch that then. Or maybe stick the data in git's merkle tree and have a really slow repo? Why bother with LFS then?
- IshKebab 5y ago> How is it supposed to work? One obvious improvement would be for Git to use the hash of the object rather than the pointer file when calculating tree hashes. That makes the storage method for the actual files independent of the commit hashes. People have mentioned several other VCSs in this thread that do it already.
- cerved 5y agookay, but why? Lots of people want to use document databases as if they were relational, lots of people want to use their RDBMS as a file server and lots of people use spreadsheets for just about everything. Lots of people wanting to use a product in certain way doesn't mean it's a good idea, nor that someone else should make that work for them that way