Update bzr timings now that code.python.org is running a newer version of bzr.
This commit is contained in:
parent
32581e6b1d
commit
3e1201f00c
|
@ -1364,16 +1364,11 @@ space was calculated with ``du -c -h``.
|
||||||
DVCS San Francisco Vancouver Space
|
DVCS San Francisco Vancouver Space
|
||||||
------- ---------------- --------- -----
|
------- ---------------- --------- -----
|
||||||
svn 1:04 2:59 139 M
|
svn 1:04 2:59 139 M
|
||||||
bzr 10:45 23:51 276 M
|
bzr 10:45 19:35 276 M
|
||||||
hg 2:30 5:24 171 M
|
hg 2:30 5:24 171 M
|
||||||
git 2:54 5:28 134 M
|
git 2:54 5:28 134 M
|
||||||
======= ================ ========= =====
|
======= ================ ========= =====
|
||||||
|
|
||||||
.. note::
|
|
||||||
The version of bzr running on code.python.org is 1.5. Changes were
|
|
||||||
made in bzr 1.9 that should bring down the time to be 80% of what is
|
|
||||||
reported.
|
|
||||||
|
|
||||||
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
|
||||||
history like all of the DVCSs do. That means svn can perform an
|
history like all of the DVCSs do. That means svn can perform an
|
||||||
|
|
Loading…
Reference in New Issue