Hi Michiel!   
      
   Michiel Broek wrote to RJ Clay:   
   MB> At least I'm curious if the old cvs is more or less fixed. I didn't had    
   MB> any success restoring it.   
      
       How do you mean "fixed"?  I as able to do 'successful' imports for both   
   your cvs and the cvs repo from Sourceforge.  The only different I found with   
   those is that yours at the later commits.  They both had the same problem   
   related to v0.34.00, which ended up on its own branch instead of the main   
   branch.  I ended up using the commits migrated from your cvs repo as the basis   
   for the master branch in the git repo.   
      
      
   MB> You shoudl be able to see all the later release points    
   MB> that are mentioned in README.developer in the mbsebbs source.   
      
       I think that matches up to, for instance, the tags in the git repo;  but   
   I'll take a look to verify.   I do see that the version that appeared to have   
   issues with it (since it did not get imported in the same branch as everything   
   else) is not in that list;  that along with how old it is, is why I don't have   
    it in the master branch of the git repo.   
      
      
      
   Jame   
      
      
       Greetings, RJ Clay   
       email: jame@ftn.rocasa.us   
      
   --- MBSE BBS v0.92.0 (GNU/Linux-i386)   
    * Origin: ftn.rocasa.net (1:120/544)