5 ms·
GitHub definitely treats large files differently from small files (it rejects them), and a Git repository you can't push to GitHub is very different from a typi
by rspeer 9y ago
GitHub definitely treats large files differently from small files (it rejects them), and a Git repository you can't push to GitHub is very different from a typical Git repository.
Other than that, Git treating large files the same as small ones is part of the problem, and the reason that centralized extensions exist. You wouldn't want "git clone" to clone the complete history of every large file, while that's not a concern at all for small files.
- icebraining 9y agoa Git repository you can't push to GitHub is very different from a typical Git repository. When comparing to Dat, I don't see how; you can't push any Dat repository to Github. Other than that, Git treating large files the same as small ones is part of the problem, and the reason that centralized extensions exist. You wouldn't want "git clone" to clone the complete history of every large file, while that's not a concern at all for small files. You don't need centralized extensions for that, though. I use git-annex, which is completely P2P.
- rspeer 9y agoI was responding to the claim that "git doesn't treat large files any differently than small ones". I was not saying anything about dat or git-annex. Now it's clear that you are treating your large files differently from small ones. Good luck with git-annex.
- deleted 9y ago[deleted]
- icebraining 9y agoRight, but the claim was about git and you responded with Github, which is a different thing.