We faced the same problem when we converted the GtkRadiant repository from
a multiple modules CVS to a single SVN repository with several independant
modules (with each their own trunk/ branches/ tags/).
What we did, is producing independant dumps for each module, and then
putting them together and recomputing the file paths and offsets of the
revision numbers to create a single dumpfile.
TTimo
On Tue, 25 Nov 2003 11:04:09 -0000
"Roger Lipscombe" <roger@differentpla.net> wrote:
> I've got a CVS repository with a couple of modules in it:
>
> /home/roger/CVS/config
> /home/roger/CVS/public_html
> /home/roger/CVS/roger
>
> I'd like to convert this into a subversion repository, but when I use:
>
> $ svnadmin create /home/roger/repos
> $ cvs2svn.py -s /home/roger/repos /home/roger/CVS
>
> ...it creates trunk/config, trunk/public_html and trunk/roger.
>
> How do I persuade it to create config/trunk, public_html/trunk and
> roger/trunk instead?
>
> Are there any ill-effects caused by simply using 'svn mv' after the initial
> import? It seems a little untidy to me.
>
> Cheers,
> Roger.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 25 14:16:02 2003