scmproj and colo plugins, problem re colo-push/colo-pull

[John Arbash Meinel]

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


> It seems to me what is really needed is an extensible way to say that
> extra revisions or data is referenced by the branch.  Then we can make
> sure to send it when the branch is pushed around.  I think the current
> nested branches spec or code does this specifically for it's own
> thing, but if it was made extensible it would allow many interesting
> hacks.
> 
> I don't see this as particularly related to having unreferenced heads.
>  bzr is happy enough to have them in the repository; the problem is
> that they need to be seen at some level as actually being referenced,
> though they're not referenced by the main revision graph.
> 

Note that there are open bugs about wanting 'tags' to also propagate the
referenced revisions.

Then again, we have some bugs where I think a plugin has a tag from the
bzr codebase, which would cause some interesting fetches.

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

iEYEARECAAYFAkt0ggsACgkQJdeBCYSNAAPQYACgwauhrWM0sUGODv1NWlrv9iPs
VqoAoJ2diDEnxCetFzKuG1jSUlE6MrP3
=YhW7
-----END PGP SIGNATURE-----