version control - Merge multiple SVN repositories with a twist -


i'm trying merge multiple source repositories together, maintaining version history during process. i've been doing lot of reading on svnadmin dump/load process, there's 1 piece i'm still missing.

each source repository setup standard "trunk" , "branches" setup. that's good. problem want massage paths when merge things together. instance...

many of approaches i've seen allow create structure this:

/project1 /project1/trunk /project1/trunk/html /project1/branches /project2 /project2/trunk /project2/trunk/html /project2/branches 

however, want our final structure instead:

/trunk /trunk/project1 /trunk/project1/html /trunk/project2 /trunk/project2/html /branches 

reason being: of projects intertwined. project1 might our backend software, project2 our front-end software, project3 our cron jobs, etc. basically, it's 1 combined system, , project specific branching seems make our life more difficult.

that said, problem arises how translate old directory structure new. thoughts?

it may meet needs merge repositories is, separate branching, move things around in new, merged repo latest revision has files want them. less work trying edit history , still preserve history, although may need turn on showing history after copy. preferred structure new revisions, if checking out old revisions puts things in wrong place.


Comments

Popular posts from this blog

c# - How to set Z index when using WPF DrawingContext? -

razor - Is this a bug in WebMatrix PageData? -

visual c++ - Using relative values in array sorting ( asm ) -