Hi Jame,   
      
   RJ Clay wrote to Michiel Broek:   
   RC> Hi Michiel!   
   RC>    
   RC> Michiel Broek wrote to RJ Clay:   
   RC> MB> At least I'm curious if the old cvs is more or less fixed. I didn't    
   RC> had   
   RC> MB> any success restoring it.   
   RC>    
   RC>     How do you mean "fixed"?  I as able to do 'successful' imports for    
   RC> both   
   RC> your cvs and the cvs repo from Sourceforge.  The only different I found    
   RC> with   
   RC> those is that yours at the later commits.  They both had the same problem   
   RC> related to v0.34.00, which ended up on its own branch instead of the main   
   RC> branch.  I ended up using the commits migrated from your cvs repo as the    
   RC> basis   
   RC> for the master branch in the git repo.   
   RC>    
   RC>    
   RC> MB> You shoudl be able to see all the later release points    
   RC> MB> that are mentioned in README.developer in the mbsebbs source.   
   RC>    
   RC>     I think that matches up to, for instance, the tags in the git repo;     
   RC> but   
   RC> I'll take a look to verify.   I do see that the version that appeared to    
   RC> have   
   RC> issues with it (since it did not get imported in the same branch as    
   RC> everything   
   RC> else) is not in that list;  that along with how old it is, is why I don't    
   RC> have   
   RC>  it in the master branch of the git repo.   
      
   It's so old I didn't bother anymore. Code upto v0.70.0 has several security   
   problems (stack overflow).   
      
   Michiel.   
      
   RC>    
      
       Greetings, Michiel Broek   
      
   Email:   mbse at fido dot mbse dot eu   
   Fidonet: Michiel Broek at 2:280/2802   
      
   ... Don't stop posting, a good laugh breaks up my day nicely   
      
   --- MBSE BBS v0.95.13 (GNU/Linux-i386)   
    * Origin: MBSE Linux BBS. Made in the Netherlands (2:280/2802)