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

Re: svnadminfilter

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-06-22 00:22:17 CEST

On Jun 21, 2007, at 05:43, claudia logan wrote:

> I am trying to restructure my repositories without loosing
> important history. I have one repository structured:
> Project A with related
> /branches,
> /trunks,
> /tags
> We have found that out of our branch a new project needs to begin
> plus we need to restructure due to common libraries, so I have
> created a separate repository with the following layout:
> Program Z:
> /trunk/project_1
> /trunk/project_2
> /trunk/project_3
> /branches/project_1
> /branches/project_2
> /branches/project_3
> ...etc
> How do I move all history that is currently in the Project A/branch
> area to now under Program Z/trunk/Project_2?
> I have tried the svnadmin dump, and the svnadmin filter (sp?). And
> is not quite working...Help!

I guess you mean "svndumpfilter" since there is no "svnadmin filter",
but I don't think you need that at all. I think you just need to
"svnadmin dump" the Project A repository and "svnadmin load" it into
the Program Z repository, probably using the "--parent-dir" argument.
Import Project A anywhere within the Program Z repository. Then check
out a working copy and use normal "svn mv" commands to rearrange it
to suit you.

If you frequently find yourself needing to combine projects like
this, you'll probably find it easier if you just put all the projects
into a single repository to start with.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 22 00:22:30 2007

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.