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

> Why not use dumpfilter to split up the old repository? That way you would have
> a seamless history, with the exception of cross-project changes, and your
> question below would resolve in a cloud of orange smoke. ;)

Yep, we're looking at that option too. But our problem is that we have a *lot* of code and a *lot* of commits, and (in my experience) high-traffic repositories will eventually reach a point where they become too large to (easily) support by sys-admins. I think this is really the same problem that any database-like system has: its easier to maintain an overall database split into several small-/medium-sized parts rather than one gigantic monolithic beast. My impression is that not many folks have thought about how to roll-over to new repositories because most folks don't have enough source-code or commit-traffic to require them to splitting things up.

> Still, this is a topic for the SVN mailinglist rather than this one.

I targeted this mailing-list first because it seemed more applicable to (and hopefully much easier to implement in) a third-party client like TortoiseSVN than directly into core SVN. My original thought was just to extend the Tortoise "svn log" functionality to allow recursing back up the "chain" because that seems like it would be the biggest win for folks I expect and (hopefully) the easiest place to implement it. Trying to implement it at the core SVN level seems like you'd end-up wanting to fully support this notion of repository-chaining across all the facets of the SVN library, e.g. would you allow doing checkout's at revisions from a "parent" repository. Trying to generically implement this notion across all of the SVN client library seems like it would get a a lot more complicated very quickly. Trying to just target the "Show Log" history-display just seemed like a much more targeted and hence hopefully smaller-scoped problem.

Can anyone familiar with the TortoiseSVN code-base chime-in here with a sense on how straight-forward it might be to extend the "Show Log" functionality as I suggested above? If the code changes are fairly straight-forward, for the purposes of my work-environment we can always roll out own custom build of TortoiseSVN and deploy that internally, meaning we could configure the functionality however works best for us rather, especially if the concern here is that it would be difficult to get this change standardly into TortoiseSVN for fear of supporting "custom" extensions which core SVN doesn't have.

Thanks,
-Tony

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

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