On Mon, Oct 1, 2012 at 1:42 PM, Michael Mol <mike...@gmail.com> wrote: > I don't know to what depth this has been discussed in the past, but if > you use git, you also get an HTTP transport, which has a useful > feature: You could simplify updating the tree on end-users's machines > by using caching proxy servers (operating in accelerator mode) on the > various mirrors.
The issue I see here is a tradeoff of bandwidth vs CPU. I just ran an emerge --sync and the total amount of transmitted data was 5M. The whole tree is 250M, though no doubt with compression that could be reduced. Now, one advantage of HTTP is that caching http servers are likely more ubiquitous in general than rsync servers. But, we have a whole bunch of rsync servers already, and we don't have a bunch of caching http servers. I suspect bandwidth is going to cost more than CPU here. In any case, not a reason to hold up git, just one more possibility if we ever move. Rich
