There's only one problem with that, and that is, how do you plan on handling forks and mergers, as well as multiple branches?
~ James On 19 Nov 2009, at 19:30, Joshua Paine wrote: > Are there scripts already to do this? Any tips for if I try to write > one > myself? My thought is to start with an empty fossil repo opened in an > empty dir. Then checkout revision 1 from svn, update to revision 2, > update to revision 3, etc.. At each step parse the update output (one > line for each file operation added/removed/modified) and transform > each > line into a fossil command, then checkin to fossil after each update. > > -- > Joshua Paine > LetterBlock: Web applications built with joy > http://letterblock.com/ > 301-576-1920 > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Lasgo Chrysalis Limited. Registered in England & Wales No. 1380166. Part of the Chrysalis Plc. Registered office: The Chrysalis Building, Bramley Road, London W10 6SP _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
