I was sort of afraid of using the svnadmin stuff because it seems
that you have to do some futzing around with the dump files if the
repos are not to be exactly the same, as is the case here. Plus
there's the whole thing about needing access to the actual repository
In any case, some more googling led me to the following script:
It's very brute force, but it works: wou give it source and
destination URLs and (optionally) a revision range, and for every
revision, it exports that revision, applies the diff to the previous
revision, and commits that to the destination repository. Takes
forever, but it did the job!
On Oct 26, 2007, at 6:00 PM, Blair Zajac wrote:
> Ryan Schmidt wrote:
>> On Oct 26, 2007, at 16:27, Bobby Rullo wrote:
>>> Pretty much the same question was asked about one year ago (er,
>>> exactly one year ago!) but I was wondering if there has been any
>>> Can one use svnsync to migrate PART of a repository (like one
>>> directory)? I'm trying to migrate a project to google code, and I
>>> want the history for but not every other project in the
>>> repository obviously.
>>> If you can't use svnsync, is there any other way to do this?
>>> original thread: http://subversion.tigris.org/servlets/ReadMsg?
>> svnadmin dump, svndumpfilter and svnadmin load would seem to be
>> the tools designed for that job. That would require that Google
>> Code allows you to import a dumpfile, however. You'll have to ask
>> them if they provide a way to do that.
> Well, you could load the dump into a fresh local repository and
> then use svnsync to sync the new repository into Google, then
> delete the the svnsync revision properties on revision 0.
> Blair Zajac, Ph.D.
> To unsubscribe, e-mail: firstname.lastname@example.org
> For additional commands, e-mail: email@example.com
Received on Sun Oct 28 02:14:05 2007