You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Lenny Tropiano <le...@rocksteady.com> on 2003/10/31 17:05:28 UTC
We're moving from CVS to SVN, having migration issues...
The cvs2svn migration is not going well. I hate to have to "checkout"
the CVS tree and import it clean into SVN without any history. (Last
resort).
Apparently I'm hitting "Issue #1440"
http://subversion.tigris.org/issues/show_bug.cgi?id=1440 and I have no
good workarounds... anyone have one that might solve my problems and
allow me to use the cvs2svn script?
--
Lenny Tropiano
Director, Advanced Technology and Networking
Rocksteady Networks, Inc.
lenny@rocksteady.com
512-275-0571
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: We're moving from CVS to SVN, having migration issues...
Posted by "Peter S. Housel" <ho...@acm.org>.
"Lenny Tropiano" <le...@rocksteady.com> wrote:
> The cvs2svn migration is not going well. I hate to have to "checkout"
> the CVS tree and import it clean into SVN without any history. (Last
> resort).
>
> Apparently I'm hitting "Issue #1440"
> http://subversion.tigris.org/issues/show_bug.cgi?id=1440 and I have no
> good workarounds... anyone have one that might solve my problems and
> allow me to use the cvs2svn script?
As a "next-to-last resort", you could use the --trunk-only option to
cvs2svn. This loses exact history of changes that took place on branches,
but should give a good conversion of changes on (and merges to) the trunk.
Other than that, I guess you (and I) will have to wait until issue 1440 is
fixed.
-Peter-
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org