question about bzr model of shared repository

Aaron Bentley aaron.bentley at utoronto.ca
Fri May 4 17:48:42 BST 2007


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

Alexander Belchenko wrote:
> I wonder why in case of shared repository branches always
> should be created inside the shared repository?

Because we want to be able to find all the branches that refer to the
data in the shared repository.

We want to be able to do garbage collection.  We can't do that unless we
know which revisions are in use.  We don't know that unless we know what
all the branches are that refer to the repository.

> What I missing here? Probably it's better (to me) to read about
> main assumptions and limitations of bzr model, does such document exists?


> 'cbranch' command looks too complex for me.

Perhaps you should just make your home directory a shared repository.
That's what everyone else seems to do, rather than trying to make
treeless repos work smoothly.  Not that I'm bitter or anything.

> I'm still don't understand policies, and in most cases
> I think I don't need them. Moreover, when I move repo/branch
> over filesystem I need to modify configuration file accordingly,

Not if you use policies.

Aaonr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGO2Pp0F+nu1YWqI0RAsOYAJ4l+pg+cBsFYE3Ml8Nu2rkLfDwSsQCfc13Q
Ts5MJ84nbwqvD6z5xG/I4mM=
=/Kq1
-----END PGP SIGNATURE-----



More information about the bazaar mailing list