Re: http://tech.slashdot.org/comments.pl?sid=1885890&cid=34358134

--- Will Palmer <wmpalmer@gmail.com> wrote:

As a simple use-case:
Everyone comes into an office in the morning and runs "git remote
update". This potentially causes a lot of traffic between the office
and their offsite central repository. If this were a p2p scenario, the
transfer from the offsite could potentially happen only once.

The same savings can be achieved by:

- Hosting the repository locally in the office;
- Automatically updating the 'official' location whenever something is
  pushed to the local repository;
- Having all developers use the office repository as their remote.

Takes about five minutes to set up.

(That does not invalidate your overall arguments, of course, but I
don't have time to address them in much detail.)

-Jan