Ray Johnson wrote:
> I'm currently working on how we can import our large VSS repository into
> Subversion.
>
> I now want to "import" the next release. When finished the second
> release should be what is in my "trunk". I realize this doesn't provide
> a "true" history. In in VSS we renamed a file it would show up in SVN
> as a completely new file and the old file being deleted. That is fine
> with us as people can always go back to VSS to find out what really
> happened (which will only happen rarely and only for a few months).
I have just done exactly what you wish to do only starting from CVS. I did a cvs export of the
first version and imported that. I then did a cvs export of the next version I wanted and overlaid
those files onto the subversion working copy. I was doing this on Windows and I actually did a cvs
export into a new directory and then used two piped Cygwin tar commands to copy those files over the
svn working copy. You can then to an svn status to find new files and add them. Working out
deleted files is a little harder but you need to do that and remove those and then to another
commit. Repeat until done.
--
Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
| sed -e 's/ x /\./g' -e 's/ at /@/'
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 16 13:53:07 2004