So it turns out the horrible checkout numbers for bzr were somewhat bogus; I

apparently have a connection to Launchpad worse than a 56K modem. Using my much
better connection to code.python.org I did the simple case for bzr and recorded
only that number.
This commit is contained in:
Brett Cannon 2009-01-25 23:40:28 +00:00
parent 25fba63409
commit 61fda6aeba
1 changed files with 3 additions and 9 deletions

View File

@ -1377,20 +1377,14 @@ space was calculated with ``du -c -h``.
DVCS Time Space DVCS Time Space
------- ---------------- -------------- ------- ---------------- --------------
svn 1:04 139 M svn 1:04 139 M
bzr 1 2:29:24 275 M bzr 10:45 276 M
bzr 2 8:46 596 M
hg 2:30 171 M hg 2:30 171 M
git 2:54 134 M git 2:54 134 M
======= ================ ============== ======= ================ ==============
.. note:: .. note::
The *bzr 1* entry is for The version of bzr running on code.python.org is 1.5. Changes were
following the instructions in the `One-Off Checkout`_ scenario made in bzr 1.9 that should bring down the reported numbers.
instructions pulling from Launchpad_ in mid-January.
The *bzr 2* entry is based on following the instructions
for the `experimental Bazaar branches
<http://www.python.org/dev/bazaar/>`_ and pulling from
http://code.python.org/python/trunk/.
When comparing these numbers to svn, it is important to realize that When comparing these numbers to svn, it is important to realize that
it is not a 1:1 comparison. Svn does not pull down the entire revision it is not a 1:1 comparison. Svn does not pull down the entire revision