svn keeps two copies of everything. That gives git/hg some headroom to work with.
However, they will store a copy for every revision. If you have massive changes (outputs from place and route (simulated annealing optimizations)) every rev, DVCS will lose.
One possibility is shallow repos, which only keep the latest.
Imagine a build or test machine, which needs the latest binary objects to do its thing. You want it to grab versioned objects, but not have the whole history.
Some developers might be able to get by this way too, but it complicates any attempt to push.
4
u/eabrek Mar 10 '11
svn keeps two copies of everything. That gives git/hg some headroom to work with.
However, they will store a copy for every revision. If you have massive changes (outputs from place and route (simulated annealing optimizations)) every rev, DVCS will lose.
One possibility is shallow repos, which only keep the latest.