[Python-Dev] PEP: Migrating the Python CVS to Subversion

M.-A. Lemburg mal at egenix.com
Sun Aug 7 16:48:13 CEST 2005

Martin v. Löwis wrote:
> M.-A. Lemburg wrote:
>>BTW, in one of your replies I read that you had a problem with
>>how cvs2svn handles trunk, branches and tags. In reality, this
>>is no problem at all, since Subversion is very good at handling
>>moves within the repository: you can easily change the repository
>>layout after the import to whatevery layout you see fit - without
>>losing any of the version history.
> Yes, however, I recall that some clients have problems with displaying
> history across renames (in particular, I believe viewcvs has this
> problem); also, it becomes difficult to refer to an old version by
> path name, since the old versions had all different path names.

Since I only use trac to view the source code (which doesn't
have this problem), I can't comment on this.

> Jim Fulton has suggested a different approach: cvs2svn can create
> a dump file, and svnadmin load accepts a parent directory. Then,
> no renames are necessary.

Good idea.

Marc-Andre Lemburg

Professional Python Services directly from the Source  (#1, Aug 07 2005)
>>> Python/Zope Consulting and Support ...        http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::

More information about the Python-Dev mailing list