<div class="gmail_quote">On Tue, Aug 17, 2010 at 11:45 AM, John Arbash Meinel <<a href="mailto:john@arbash-meinel.com">john@arbash-meinel.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 </div>... <div class="im">> > And one further option. Switch to using lightweight checkouts and > treeless branches. You'll likely be better served by this in the long > run (since we don't have to recreate the whole tree content, just the > few files which are actually different). But some of it will depend on > your specific needs. (And yes, it doesn't solve the problem if you still > experience the limbo issue on the first checkout.) > > >> We've been avoiding lightweight checkouts, because we have times of day >> when our internal network is saturated anyway, which makes any >> operations which need the network problematic. I know that's our >> problem and bzr can't do anything about it, but that's why we favor full >> branches. > >> Thanks, and i will try to reproduce the observation a few more times >> today and report back. > >> ~M </div>You would still have a local repository and full content. You would just only have a small handful (1) of working trees that then point at a given (local) branch. It is how I develop using bzr (using ~3 working trees, and many many branches.) <div class="im"> John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a> </div>iEYEARECAAYFAkxq2K8ACgkQJdeBCYSNAAOP3wCfTvFikaSUtsQjNymjHm0PX2G1 xzoAoNDRwnN/xXCP0DH+HO/JVvlPzfU7 =SKh8 -----END PGP SIGNATURE----- </blockquote></div> Ah, yes. You are correct of course. My test setup (multiple full branches of a trunk, all within the same shared local repo) is a bit unrealistic. More likely, each of our developers would choose to keep one branch (treeless or not) in sync with a central (remote) branch and create multiple lightweight checkouts of the local branch. As you point out, that still does not address the need for a first full branch, but it is much better than my artificial test situation. I just did an experiment. On the command line, I did three more iterations of "bzr branch <from_location> <to_location>" with both locations in the same shared repo on a local disk. During these operations, I aggressively navigated through the limbo folders, watching them get created, populated and ultimately deleted. Every iteration completed with no errors and no warnings. In fact, when the folders were deleted, my Windows Explorer window abruptly evaporated -- that is standard behavior on Windows. Note that I did not have any DOS or Cygwin shells open under the .bzr directory in any of my experiments; that could be a different story which I do not want to read today. So unless I see this again, I will regard it as a fluke. But if it does happen again, I will probably send a jittery email begging for advice. :) Thanks ~M