On Jan 11, 2008, at 16:34, Peter Wemm wrote:
> I'm trying to organize a switch from a cvs repository to svn, but we
> have the problem that we have a considerable infrastructure built
> around cvs. Realistically, we can never be rid of it. So, besides
> converting our 15 years of cvs history to svn, a prerequisite is to be
> able to continuously export svn changes back to the cvs tree and make
> it "look real".
>
> We did something like this for using perforce. We have a process that
> polls the p4 server for changes, then extracts them one at a time when
> it finds them and commit them to the cvs tree. (We do this at work
> too, where its been going happily for 7 years now. We still cut
> releases from the replicated cvs tree, not perforce)
[snip]
> Any suggestions or pointers would be greatly appreciated. Even "don't
> use tool XXX" tips!
I would suggest: don't do this at all. Use cvs2svn to convert your
existing CVS repository to a Subversion repository. Then use the
Subversion repository only. cvs2svn is a well-tested and often-used
script so I hope it will work for you. If you have questions about
cvs2svn, it has its own mailing list.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-12 01:21:42 CET