Idea: "Show Log" History from Child->Parent Repository

Hi,

Background: We have a large internal enterprise SVN repo (~300GB on disk, ~450,000 revisions) and we're worried about it becoming too large to manage/support. So, we're planning to cut over to a new repo (i.e. freeze the old repo, do an export from trunk in the old repo, import into trunk in the new repo, and have developers migrate to use the new repo going forward) sometime over the next year and we've been thinking about ways to make it dead-easy for our developers to access the history in the old repo. Using the Repo Browser to manually navigate to the old repo URL and using Show Log from there seems to be the best current solution, but I'm wondering if TortoiseSVN couldn't be extended to do something more transparent...

Would it at all be possible to extend/leverage TortoiseSVN's "Show Log" functionality such that: when you're viewing the history of /trunk in the "new" repo and once you hit the end of the revision-history in the current repo that Tortoise could somehow transparently follow a pointer to a "parent" repository URL and start seamlessly displaying the history of that URL in that "parent" repository? In other words, once we fall off the "end" (i.e. revision 0) of http://repo2/trunk we'd seemlessly start displaying the history of http://repo1/trunk@HEAD. Maybe something like setting a "svn:parent-url" property on http://repo2/trunk on the revision that first creates /trunk in the new repo. This way, when Tortoise is looping over the SVN history and it finds a revision with this "parent-url" property set with a non-null value, then that's the sign to stop reporting history in the current repo/URL and jump over to the parent-url and start reporting history from there.

Something like that would allow admins to create an arbitrary "chain" of linked repo's, where users could seamlessly drill down into the history of "trunk" which logically would span multiple physical repo's. With Tortoise's "Show Log" seamlessly abstracting all the behind-the-scenes details, users could do slick things like do "Show Log" on a single file, highlight two different revisions (even though they're physically in separate repo's) and right-click and use "Compare revisions" to get a GUI diff of those two revisions.

Any thoughts?

Thanks for listening!
_________________________________________
Tony Duckles | Epic Systems Corporation
E-mail | tduckles_at_epic.com

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2703359

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-02-11 03:11:38 CET