Shallow branches question

[Nicholas Allen]

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

| I'm not sure that bringing in a Daemon is the correct fix for this sort of
| thing. I think it might fit well with an integrated gui like 
TortoiseBZR, but I
| don't think it fits well as a generic solution.
I don't understand why not? The deamon would be started by bzr when you 
branch and continue fetching revisions in the background after bzr 
branch command returns. So as long as the daemon runs as long as the 
original branch command would have then you would have all revisions. So 
the chances of loosing revisions permananently are reduced. Also you 
could specify an --wait option to branch that made bzr behave the same 
as now. I just think the background downloading of revisions makes more 
sense as the default behavior because then Bazaar is the first DVCS that 
would have the performance of a centralised one but all the other 
advantages that DVCS gives you.

Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFH2BTmbpmWsXfOU58RAlMRAKCllRQlazBtDJahMcc3nLlooNNl5ACgr64a
fuQvNxbkFb5XcqIu0ss6QqE=
=Lzcf
-----END PGP SIGNATURE-----