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 eGenix.com 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 ! :::: _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
