I have a "docs" folder in a Subversion repository named "project". I've come to the conclusion that it should really be kept under a separate Subversion repository named "project_docs". I'd like to move the "docs" folder (and all of it's revisions) to the "project_docs" repository. Is there any way to do this?
views:
6305answers:
5
+1
A:
I don't believe you can do it remotely (i.e., without a local copy). But this should work: svn export the folder from the original server, then svn add it to your new repo.
Like:
$ svn checkout svn://example.net/newrepo .
$ svn export svn://example.com/oldrepo/mydir ./mydir
$ svn add ./mydir; svn commit
Edit: D'oh, this drops the history. Use svnadmin as Samuel describes.
Peter Stone
2009-01-06 19:09:40
this does not keep all the revisions, which he needs to preserve..
petr k.
2009-01-06 19:13:27
However, you cannot keep the revisions without access to the repository itself. If you can only have a working copy, this is the best he can do.
Samuel
2009-01-06 19:15:41
+2
A:
This is discussed in the svn documentation. Check out the Repository Maintenance section on svndumpfilter... It specifically describes how to dump projects out of a central repository and move them into new, separate repositories.
Adam Bellaire
2009-01-06 19:10:58
+29
A:
If you have access the repository itself (not a working copy), you should be able to dump the current repository, filter it to only include information about the docs folder, and load it into the other repository.
Would be something like this:
svnadmin dump /svn/old_repos > ./repository.dump
svndumpfilter include path/to/docs --drop-empty-revs --renumber-revs --preserve-revprops < ./repository.dump > ./docs_only.dump
svnadmin load /svn/new_repos < ./docs_only.dump
Without access to the repository, you cannot maintain the revision history and you have to settle for copying the files into the new repository and committing.
Samuel
2009-01-06 19:14:49
Nice example. Note that as stated in the documentation I linked to, this solution will re-number all of the revisions so that there are no "empties". Something to keep in mind if you reference the doc revisions anywhere else.
Adam Bellaire
2009-01-06 19:20:03
I suggested the removal of empty revisions to avoid adding a bunch of empty revisions to the target repository, most likely confusing anyone that didn't know about the load. Since --preserve-revprops will keep the commit messages instead of the using the default one of loading.
Samuel
2009-01-06 19:22:53
Thanks for the answer. In case anyone needs to know, if you need more then one folder just put a space between them in the include list.Ex. ... include folderOne folderTwo
Robin Robinson
2009-07-16 18:40:15
Renumbering revisions is probably a bad idea, as commit messages and issue tracking tools may refer to them
Wim Coenen
2009-12-27 15:12:21
+8
A:
svndumpfilter has a serious flaw - if a file or path was copied from a path you're filtering out to one you're filtering in, svndumpfilter won't be able to fill out the history and the job will fail.
You can use svndumpfilter2 if you experience this problem.
compie
2009-04-02 09:00:58