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. >
Just several other possible use case: 1) Consider a project that was developed outside of ASF, and then imported int ASF repository using "snapshot" of sources on that date. Can we link to the old repository somehow? 2) Tomcat 6.0 source code http://svn.apache.org/viewvc?view=revision&revision=389140 http://svn.apache.org/viewvc?view=revision&revision=389146 It was imported as snapshot, without proper links to Tomcat 5.5 sources. There was a cause for that: Tomcat 5.5 used different project layout: module/(trunk|branch|tags)/... while in Tomcat 6.0 it is just a single /trunk. All source code is now in a single tree "/trunk/java" tree, whereas before the packages were split across several modules. Sometimes I miss that viewvc cannot show the history of a certain line of code earlier than r389146 and I have to manually switch it to some other code tree and to continue my search there. I agree that if this were implemented, it could be a revision property so that administrator could change it any time if server configurations are changed. There is that "server-side config which 'broadcasts' to clients" [1974] enhancement request, and how is that configuration stored on the server? Maybe some external configuration file? Or configuration file stored in this/other repository that is announced using some svn property set on r0? [1974] http://subversion.tigris.org/issues/show_bug.cgi?id=1974 Best regards, Konstantin Kolinko
