3 ms·
Just determining the shape of "git for data" has been a nontrivial exercise. We found that, if you do the naive translation, you get a "one size fits none," bec
by akarve 7y ago
Just determining the shape of "git for data" has been a nontrivial exercise. We found that, if you do the naive translation, you get a "one size fits none," because data and code are fundamentally different.
What would be your main use cases with said "git for data"?
- heinrichhartman 7y agoOne use-case is this one: https://github.com/HeinrichHartmann/arxiv_meta https://github.com/HeinrichHartmann/arxiv_meta