There are things we need to work on, but some of the information here is misleading.
1) What is "bzr clone" time in a shared repository (do
bzr init-repo --trees .
bzr branch upstream test1
time bzr branch test1 test2
I would imaging that we might actually be faster than hg within a shared repository. I would expect us to at least be close.
hg uses hardlinks, which aren't safe when accessed remotely. We've discussed if we can do it in a different way (perhaps
having a flag that this repository isn't remote-access safe, etc).
2) Actually, the way we measure revisions is different. bzr has almost 2.5x the number of revisions. Specifically, bzr distinguishes between mainline revisions (things committed on *this* branch), and merged revisions. bzr has 2487 mainline revisions, and 11326 total revisions.
You can get that with "bzr revision-history | wc -l" and "bzr ancestry | wc -l" respectively.
'bzr log' numbers based on mainline revisions.
There are things we need to work on, but some of the information here is misleading.
1) What is "bzr clone" time in a shared repository (do
bzr init-repo --trees .
bzr branch upstream test1
time bzr branch test1 test2
I would imaging that we might actually be faster than hg within a shared repository. I would expect us to at least be close.
hg uses hardlinks, which aren't safe when accessed remotely. We've discussed if we can do it in a different way (perhaps
having a flag that this repository isn't remote-access safe, etc).
2) Actually, the way we measure revisions is different. bzr has almost 2.5x the number of revisions. Specifically, bzr distinguishes between mainline revisions (things committed on *this* branch), and merged revisions. bzr has 2487 mainline revisions, and 11326 total revisions.
You can get that with "bzr revision-history | wc -l" and "bzr ancestry | wc -l" respectively.
'bzr log' numbers based on mainline revisions.