Brief article on benchmarks of Python repository with leading DVCSen

[Nicholas Allen]

I used Mercurial,
> and all I did was go to my "random junk" directory, do hg clone
> http://,,,python... python-patch, cd python-patch, hack, then create &
> upload the patch to the tracker.
>
> For Bazaar, I believe I'd need to add the steps
> bzr init-repo python-repo
> (do some fiddling to download and populate this repo with a pre-build tarball)
> (bzr pull the rest of the data from since the tarball was made)
> bzr branch python-patch
> ... etc much as before
If all you did was create one branch in Mercurial and hack in it then 
the exact same would be true for Bazaar.

bzr branch http://python.... python-patch
cd python-patch
hack, hack

A repository is optional but can improve the disk usage and performance 
of Bazaar. So Bazaar does not dictate your directory structure (as you 
do not need to use shared repositories if you don't want).

Also a shared repository can be any directory (even you home directory 
if you like). So you could even do this once and forget about it forever 
for all projects and branches. Bazaar does not dictate the directory 
structure below the repository in any way.

Nick