I know others have recommended moving, renaming then moving, etc.
One other possible solution is:
1. Dump the existing repository:
svnadmin dump PathToOldRepo > OldRepoDumpfile
2. Create a new repository
svnadmin create PathToNewRepo
3. Create a "trunk" directory in the new repo
svn mkdir file:///PathToNewRepo/trunk -m "Creating trunk"
4. Load the old repository into trunk of the new repository
svnadmin load PathToNewRepo --parent-dir trunk --force-uuid <
OldRepoDumpfile
If you don't use the --force-uuid, then you won't be able to switch any
working copies to the new repo
________________________________
From: jbonnett@sola.com.au [mailto:jbonnett@sola.com.au]
Sent: Thursday, May 18, 2006 11:39 PM
To: users@subversion.tigris.org
Subject: Creating trunk later
Although I have used SV for a while I now know I have been doing things
wrongly and would like to correct it.
I'll bet I am not the only one to have done this or asked this question
but I can't seem to find an answer in the archives.
I created my repository and checked my working copy into
https://repository/prog1
I now realise I should have used https://repository/prog1/trunk then I
could have easily made branches and tags.
I have a history of revisions built up in https://repository/prog1 and
would like to move everything to https://repository/prog1/trunk
including my revision history. I don't seem to be able to do this. The
revision history seems to want to stay in the old location.
John Bonnett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 19 15:34:02 2006