RetroSearch Browse

Fri Jul 29 23:15:18 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-July/054998.html

Martin v. Löwis wrote:
> Jim Fulton wrote:
> 
>>I did convert projects individually.  I told cvs2svn to just create dump
>>files.  I then used svnload to load the dump files myself so that
>>I could make each project a top-level directory with it's own
>>trunk, branches and tags.
>>
>>I'd be happy to share my scrips, although there's nothing all that
>>complicated about them.
> 
> 
> If that's how it worked, I'm sure I can cook my own. Just for
> confirmation:  the svn revision numbers don't increase
> chronologically across 'modules', right: i.e. the first
> revision of the module that was converted second has a higher
> revision than the last revision of the first module, even
> though historically, the order should have been reverse.
> 
> Not that this worries me much, but I'd like to confirm there
> is no other way.

Right. The revision numbers reflect the order in which they are
added to the svn repo.  I'm pretty sure the revision meta data,
in particular the date, was retained.  This is an advantage
advantage of using the low-level dump/load mechanism.

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-July/054998.html below:

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