Sounds like you want to use an approach called "vendoring". http://svnbook.red-bean.com/en/1.7/svn.advanced.vendorbr.html
Effectively, you get dumps from the "vendor", and vice-versa(?). You shouldn't care / need to care what their source looks like, or even where it comes from. You just want to make your copy of the latest source in your repository look like what the vendor has. If the vendor (or you) decides to switch to some other version control system (such as Git), it should be irrelevant to the other party. On the other hand, what you're describing is a typical scenario for distributed version control. So you might want to look into Git or Mercurial. Mercurial is slightly more natural for Subversion users. Eric. On Mon, Jul 20, 2015 at 8:08 AM, Mani Raju <mani...@gmail.com> wrote: > Hi, > My company & vendor planning to maintain 2 independent SVN > repositories(URLs & server names are different) & need to merge between 2 > repositories. > > Is SVN 1.8 support merging between 2 repos at trunk or branch level? > Is any tool provides auto sync or auto merging without manual intervention > > Tried with TortoiseSVN by creating 2 repositories, merged & getting the > below error.Refer attached. > > ERROR --> svn: 'x' isn't in the same repository as 'y' " > > I got the below link to sync between branches from different > repositories.Provided solution in this link is to maintain > the same UUID for both repo.So I am guessing we can sync at branch level. > > > http://stackoverflow.com/questions/3907162/svn-error-x-isnt-in-the-same-repository-as-y-during-merge > > > I am not a SVN admin.Just evaluating the products to recommend to my > team.Please advise if I am wrong. > > Thanks in advance! > Mani >
