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

Re: Combining Repositories

From: Andrey Repin <anrdaemon_at_freemail.ru>
Date: Thu, 2 Apr 2009 17:47:07 +0400

Greetings, Zarikian!

ZNS> I would like to take three separate repositories and combine them under
ZNS> one common repository. They will remain in separate areas so there is no
ZNS> merging, overlap, or overwriting required. Is it as simple as just
ZNS> moving the repositories around?

ZNS> A crude visual in case I wasn't clear:

ZNS> Repo A
ZNS> Repo B
ZNS> Repo C

ZNS> into...

ZNS> Repo D

ZNS> - Folder A
ZNS> - Folder B
ZNS> - Folder C

ZNS> Thank you... I appreciate it.

If they are separate repositories, you may go through svnadmin dump for each
of them, then import these dumps back into folders in new repository.

But, honestly, if these are purely separate projects, better not merge repos.
Major issue with this move is that every change in each of these projects will
increase revision number for each of them at commit times.
And it'll be hard to tell, which project it was from just a revision number.

Only usual case for such step I see if you really want to physically join all
these projects, including, as next step after this reinport, folder
rearrangement to better suit the new big project (of what you want to keep
tracking), and future updates causing changes in it as a whole entity.

My advice: Think twice :)
SVNParentPath is what you need most likely.

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 02.04.2009, <17:36>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1519174
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-02 15:52:06 CEST

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

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