Exacly. Git supposed to be DVCS not generic DVFS. Choose right tool for right task. I needed generic DVFS to store my docs, so I wrote one. Its easy and quick and does it job :)
> He said that GitLab hosts one repository with about 20-million references; each time a reference is deleted, the packed-refs file has to be completely rewritten which means rewriting 2GB of data. "To add insult to injury, this repository typically deletes references every couple seconds."
Very excited for git 3.0, and also ready to be immediately frustrated by it :D
`jj` has done git users an amazing service simply by being a more intuitive VCS front-end is possible.
Storing large files somewhere else is a step towards the centralized model. But it's against initial design principles of git.
Exacly. Git supposed to be DVCS not generic DVFS. Choose right tool for right task. I needed generic DVFS to store my docs, so I wrote one. Its easy and quick and does it job :)
> He said that GitLab hosts one repository with about 20-million references; each time a reference is deleted, the packed-refs file has to be completely rewritten which means rewriting 2GB of data. "To add insult to injury, this repository typically deletes references every couple seconds."
What in the world... why?
And also: why should he or git care?
Git needs to track software licenses on a per commit basis.