[MERGE] Remove interdependency between WorkingTree and RevisionTree

[Aaron Bentley]

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

John Arbash Meinel wrote:
> The old code created a RevisionTree directly, but to do a lightweight
> bzr checkout of an svn repo, Jelmer needs to create an SVNRevisionTree,
> rather than a bzr RevisionTree, because it is attached to the
> repository, re-using Repository.revision_tree seemed a better way to
> factor it, rather than having WorkingTree explicitly depend on RevisionTree.

Personally, I'd really like to know why an SVNRevisionTree is necessary.
 RevisionTree is basically a client of the public Repository interface,
so you would think an SVNRepository would be fine.

I'm not against having an SVNRevisionTree, I'd just like to know why, so
we can determine whether RevisionTree should be adjusted to make it more
generic.

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

iD8DBQFEu6BT0F+nu1YWqI0RAkFiAJ0fYYNGJl5StEwOJAPG5wMbiOJnOgCgh4kU
86XkoaRutcn2ueeEPd0KBXE=
=xzWI
-----END PGP SIGNATURE-----