Re: about the need for a "takeover" command

> >Of course I can't wait for it to be developed and released, so my problem
> >stays, but I'll find a dirty way to do it.
> >
> >My guess for the moment is that I should have an exact point where all
> >files are exactly the same in the CVS and in the SVN repo, then checkout
> >the SVN repo at that point, remove all files (except the .svn/
> >directories), and redistribute these .svn/ directories in the existing
> >(CVS) working copy. If you know any script that does this kind of ugly
> >stuff, pls let me know.
>
> cd a-new-svn-checkout
> find . -name .svn -print0 | tar -T - --null -cv | tar -C
> ../my-existing-cvs-working-copy -x

Thanks! I decided to make a zip file of only those .svn directories, and
have people switch from CVS to SVN code base by doing :

1) cvs update
2) unzip
3) remove CVS/ directories
4) svn stat (to verify their patches)

and it seems to be working well!

Keep up the good work

-- Fil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 21 17:49:22 2005