Branch generates ImmortalLimbo warning ?

[John Arbash Meinel]

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

...
> 
> 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

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.)

John
=:->

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

iEYEARECAAYFAkxq2K8ACgkQJdeBCYSNAAOP3wCfTvFikaSUtsQjNymjHm0PX2G1
xzoAoNDRwnN/xXCP0DH+HO/JVvlPzfU7
=SKh8
-----END PGP SIGNATURE-----