[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Thought experiment - follow logs back before r1 into previous repository

From: Konstantin Kolinko <knst.kolinko_at_gmail.com>
Date: Fri, 30 Sep 2011 14:15:48 +0400

2011/9/30 Julian Foad <julian.foad_at_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

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:
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?


Best regards,
Konstantin Kolinko
Received on 2011-09-30 13:05:18 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.