subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Schmidt <subversion-20...@ryandesign.com>
Subject Re: Importing Existing Repository into a New Repository
Date Wed, 06 Oct 2010 12:27:40 GMT

On Oct 6, 2010, at 07:03, Nico Kadel-Garcia wrote:

> 2010/10/5 Ryan Schmidt:
>> 
>> If you do not want to preserve the history, then you want to "svn export" from the
old repository and "svn import" it into the new repository.
> 
> You'll also want to seriously review the Subversion properties of the
> material before the export, in order to replicate them in the imported
> or "added" material. svn:externals, svn:keywords, svn:eol, etc., etc.,
> etc. are not contained in an export: they're meta data in the
> Subversion repository, not the raw or even processed content of the
> exported files. This includes svn:eol, svn:keywords, and in particular
> svn:external. svn:keywords in particular, will create fascinating and
> confusing content in the keywords of the files at the time of your
> original import, so this is something to do cautiously.
> 
> This is one of those cases where a bit of extra attention, instead of
> "just export it and import it" can save you some surprises down the
> road.

Ah yes, this is true. If properties are of interest, then an alternative to svn exporting,
manually fixing the properties, and svn importing, is to svnadmin dump just the HEAD revision
and then svnadmin load it:

svnadmin dump -rHEAD /path/to/oldrepo > dump
svnadmin load /path/to/newrepo < dump

This will dump only a single revision representing the state of the old repo at HEAD, and
will preserve properties. In between dump and load you can use svndumpfilter if you wish to
exclude parts of the dump (or include only certain parts), and you can use svnadmin load's
--parent-dir argument if you want to change where the contents are loaded (or just use "svn
mv" after loading).




Mime
View raw message