[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r8632 - trunk/tools/cvs2svn

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-02-13 19:25:43 CET

kfogel@tigris.org writes:

> Author: kfogel
> Date: Fri Feb 13 11:26:50 2004
> New Revision: 8632
> Modified:
> trunk/tools/cvs2svn/dump-db.py
> Log:
> Extend debugging tool as part of work on issue #1510:
> * tools/cvs2svn/dump-db.py
> (main): Handle unmarshalled data too.

When I saw this, I started to revert my cvs2svn.py change of revision
8547 (which started marshaling the revisions db data so dump-db.py
could deal with it), but it seems that some of our revision data
*does* look similar enough to marshaled data -- when I reverted the
that change locally, I actually got a SEGFAULT in Python (repeatedly,
not a fluke case) trying to use dump-db.py on now-unmarshaled

I think for consistency (yes, at the cost of the marshaling), I'd
prefer to keep all our .db data marshalled. Besides, if we change the
format of those database values, we don't have to remember to start
marshaling it later.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 13 19:26:37 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.