how does this go together with mercurial plugin?

Well, I really do not plan to support any other version control backend but Subversion. I'm really happy w/ SVN, I don't plan to use any other backend - no spare time to try and/or investigate other backends, sorry.

I guess there would be -at least- some issues with the way the plugin manages the changesets (changeset sorting is based on the monotonic version number increase of SVN - not on the changeset date - so I guess it may not be compliant with other backends). There is only one direct access to the SVN repository (vs. accessing the repository through the VC abstraction layer and the repository cache) in model.Repository.get_revision_properties(), as the abstraction layer does not manage revision-wide properties. I guess this could be easily bypassed or abstracted for another VC backend.

If anyone is interested in porting the plugin for an alternative backend, it could be integrated within this plugin.

I've added some technical details about support for Hg in RevtreePlugin/Limitations

I've removed the last direct Subversion backend dependency in [1866].

This does not mean that the plugin may be used w/ Hg though, as the revision numbering scheme has yet to be addressed.

See also t:ticket:1492