Konstantin Kolinko wrote on Fri, Sep 30, 2011 at 14:15:48 +0400: > 2011/9/30 Julian Foad <julian.f...@wandisco.com>: > > Perhaps we'd set > > a revprop on (new) r0 or r1 pointing to the old repo URL so that this > > info is configured in a single place. The two sets of revision numbers > > in the output would be confusing so we may want to consider tagging the > > old and/or the new revnums with some marker as well as inserting an "And > > now from the old repository:" message.
Of course, this should nest to an arbitrary-length chain of repositories. :-) Another problem, when you chain repositories this way, I could see how it would be more natural for the "second in the chain" repository to have a non-empty r0; but the assumption that the contents of r0 are fixed --- precisely the root fspath and nothing else --- is ubiquitous in the codebase. Thirdly, once you allow a chain of repositories, you can as easily allow a tree of repositories (where *two* repositories state that repos5 is their predecessor). From here the distance is short to asking if DAGs can also be supported, and --- if that's a yes --- then to further ask if more complex graph topologies (that DVCS's support) can also be supported :-).
