What do I call a working tree that stores its revisions in a shared repository?
Stefan Monnier
monnier at iro.umontreal.ca
Tue Apr 1 06:53:33 BST 2008
>> > Ah, sorry. I see. My point was different - I don't like shared
>> > repositories because of the organisational limitations they impose, so
>> > I prefer to use standalone branches. However, they are too slow to
>> > use, so to get a reasonable level of speed back, I'm considering using
>> > an OS copy rather than a bzr branch.
>>
>> I suggest the following hack:
> Why not use lightweight checkouts instead of this hack?
Not sure how that would work since it seems this requires to still have
a branch underneath the repository. Are you suggesting something like:
bzr repo-init ~/var/bzr-foo
bzr clone <bar> ~/var/bzr-foo/bar
(cd ~/var/bzr-foo/bar; bzr remove-tree)
bzr checkout --lightweight ~/var/bzr-foo/bar <anywhere>
Would this work?
The thing is: I don't have a clear enough understanding of lightweight
checkouts to figure out whether it would behave identically to what
I proposed (what happens when you do `bzr merge', `bzr pull', `bzr
push'?).
Stefan
More information about the bazaar
mailing list