CVS conversion: merged branches not in shared repo

[Aaron Bentley]

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

Greg Ward wrote:
> someone fixed a bug there, merged it to the
> next release branch (3-7-1), and there have not been any changes on
> 3-6-1 since then.

> I assume the history of branch 3-6-1 is indeed present in my shared
> repo.  But how do I clone that branch to fix another bug on it, if
> there is no "3-6-1" directory in the shared repo?

I'll call the 3-7-1 branch $BRANCH.

Do "bzr log -n0 $BRANCH" for bzr.dev or "bzr log --long $BRANCH" for
earlier versions to find the revno of the revision that was merged, i.e.
the one that should be the head of 3-6-1.  I'll call it $REVNO.

Now do "bzr branch $BRANCH -r $REVNO 3-6-1".

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

iEYEARECAAYFAknTcr0ACgkQ0F+nu1YWqI1VywCeIS7l4E+b9+fKa5+Pwpn1yxt/
3tkAn2PXdb1+2SGMUtP/U8JjwBdeszh+
=vkp2
-----END PGP SIGNATURE-----