Call for testing of colocated branch support in bzr.dev

[John Arbash Meinel]

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

...

>> Anyway, +1 on just creating a Branch at NULL_REVISION.  It
>> certainly won't be a worse experience than what happens now.
> I think this would be a good idea too.
> 
> I'm not sure about periodically updating the branch during fetch,
> but at least creating an empty branch with the right stacking data
> would be nice.
> 
> Cheers,
> 
> Jelmer

*today* it wouldn't work anyway, because we don't transmit revisions
in such a way that we can snapshot the transfer. However, we can add
that, and even if we don't update the branch (but we do commit to the
repository), then it will work appropriately to resume a
half-transmitted stream.

But it would involve changing streaming in some fashion (though in
many ways for the better, since you wouldn't have to think about 100k
revisions all at once, etc.)

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

iEYEARECAAYFAk9Ck+gACgkQJdeBCYSNAANHpQCgo/Hs4BjjXcMn7ADA896vklFL
zbUAnRsaElJYsFKzZveH6Thh3VZP+NJy
=HF3L
-----END PGP SIGNATURE-----