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

Re: cvs2svn: raw or cooked?

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2000-09-26 17:11:17 CEST

Greg Stein <gstein@lyra.org> writes:
> btw, I agree with Jim: crawl the ,v files to get all the data; using cvs
> commands just doesn't feel right and it doesn't seem like you could really
> get at all the data. (but I'll admit I don't know that for sure)

No, you can definitely get all the data. It's just slower going
through CVS, is all.

> It might also be nice to take this moment to define the XML interchange
> format for an SVN repository. If the tool was cvs2xml, then we
> could do "svn import-xml my-cvs-repository.xml". And anybody could do "svn
> export-xml ..." followed by an svn import-xml somewhere else.
>
> Just to make your job harder... :-)

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 (?).

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.
Received on Sat Oct 21 14:36:09 2006

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