Re: cvs2svn: raw or cooked?

> Hey! Bob, I think Greg's right. In fact, using XML for the generic
> interchange format has been discussed before. And creating a big XML
> file, or zillions of XML files, is defensible for a one-time
> conversion script (?).

The Red Hat comp-tools repositority is about four gigabytes. And XML
is renowned for its bloat. So you can expect to see some *very large*
datasets. But it would compress well... Dia and Gnumeric both use
compressed XML for their file formats.

Perhaps this could be done in a way that allows one to pipe one
process to another.

> Note that each commit is represented by one complete <tree-delta> xml
> form. We can write up the DTD for you really quickly, it's easy.
>
> Probably writing cvs2xml (where the XML uses the Subversion tree delta
> DTD) would be the best thing. Once we have the XML, from any source,
> we can import it easily into the repository.

Eventually, we'll need to find some way to capture non-historical
properties too. Bob might find it convienient to express some CVS
things as non-historical properties, though I don't know what.
Received on Sat Oct 21 14:36:09 2006