On 01/11/2010, at 5:43 AM, Rene wrote: > I have moved my fossil repository for cvs conversions to > https://chiselapp.com/ under the name csv2scm. If you want to convert a cvs > repository give it a go. I have done successful conversions on the public > freebsd cvs repositories project/compat-fbsd en projects/binup. And the > largest I have done is the public postgres cvs repository. That took on my > Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz with 2 GB > > 20 minutes to construct a meta database (cvs2sqlite) > 1,5 hours to get the change sets (commits) > 4,5 hours to do the actual import (db2fossil) > Unfortunately https://chiselapp.com/ has an old fossil binary from May. The > documentation isn't shown as homepage an error instead "No such document: > tip/doc/wiki/index.wiki" >
On the Tclers Chat, Konstantin Khomoutov (kostix) mentioned a link describing "Lessons from PostgreSQL's Git transition" ( http://lwn.net/Articles/409635/ ) and noted they mention CVS repo accumulated some crap over time which requited manual intervention, besides other issues, and wondered if a big project like Tcl/Tk could suffer from the same syndrome. A few of us in the Tcl/Tk community have been wondering how Fossil would cope with a Tcl/Tk repositiory, Based on your experience with Postgres, are there any lessons to be learned? Steve
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
