Evaluating Bazaar in a CVS environment.

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Neil Martinsen-Burrell wrote:
| Andy Walker <walkeraj <at> gmail.com> writes:
|
|>> Right, you use "bzr switch" to change the branch the checkout is
|>> associated with. It will carry across uncommitted changes (by design, so
|>> if you did a fix in the wrong location, you can switch and commit it in
|>> the right place.) Useful when you realize you just started a new bugfix.
|>>
|>> So you have to take some care when switching with uncommitted changes.
|>> (Sometimes you might go to switch not realizing that you didn't
commit yet.)
|> So, in this environment, each time I create a new branch, will Bazaar be
|> creating empty directories for each branch's .bzr directory to live in?
|
| That is correct, although new branches made inside a shared repository are
| *extremely* space efficient.  All of the revision information that is
common
| between the branches is stored only once.  For example, I have a shared
| repository in ~/src/bzr that I use to do Bazaar related development.
There is a
| pristine branch of Bazaar's development version there at
~/src/bzr/bzr.dev and
| if I were using John's single working copy approach, I could make as many
| branches as I wanted at approximately 260 KB per branch.  I currently
go ahead
| and make full tree-containing branches for every bugfix I do, but
John's recent
| discussion of the usefulness of `bzr switch` for him has been compelling.
|
| -Neil
|

260KB per branch? That sounds pretty big, using du with and without
apparent, I see a few branches as somewhere between 5-13KB each. You
might be using Branch5 branches, which stored the full
'revision-history'. New ones just store the tip, and are even better at
storage efficiency.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhmlCcACgkQJdeBCYSNAAOlewCgl/ENzpLQffKgQjKqIMFoF+BG
9hsAnA/eGi4Jxy99LFVmVm/2EDJR+isZ
=nGbE
-----END PGP SIGNATURE-----