RE: re-organizing a repository

I'd recommend moving your files using Subversion commands. That way you'll keep the history.

If you are using a Subversion client like TortoiseSVN, I strongly recommend doing this type of reorganization directly in the repository browser or equivalent tool that acts directly on the repository. Moving large directories around and managing a working directory at the same time can be really cumbersome and slow-also prone to errors. Better to do the reorganization directly to the repository and then either checkout fresh, or do the update on your working directory in a single pass.

If you're using the SVN command, I believe you'll get the same effect using URLs instead of local working directories.

KRP

From: Jeremy Mordkoff [mailto:jlm_at_ZeeVee.Com]
Sent: Tuesday, October 06, 2009 2:50 PM
To: users_at_subversion.tigris.org
Subject: re-organizing a repository

Right now, I have a repository organized like this:

Zcode
Zcode/comp1
Zcode/comp2
...
Zcode/comp9

I would like to make one component a peer of zcode, e.g.

Zcode
Zcode/comp1
...
Zcode/comp9
comp2

this component has 10,000 files in 4000 directories. Is just doing an svn mv feasible? How about an svn copy instead? Is there a better way, with or without history?

JLM

Jeremy Mordkoff
Director, QA, IT & Release
ZeeVee, Inc.
One Monarch Drive | Littleton, MA 01460
Office: 978.467.1395 x233 | Fax: 978.467.1404
Mobile: 978-257-2183
jlm_at_zeevee.com<mailto:jlm_at_zeevee.com>
www.zeevee.com<http://www.zeevee.com/>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2404272

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-06 22:13:47 CEST