Hello Bob!

Oct 10 10:17 03, Bob Jones wrote to Bo Simonsen:

 BJ>> You will need to get in the habbit of running make 
 BJ>> clean followed by a
 BJ>> make build after making updates to CVS to test that we didn't break
 BJ>> anything.....

 BS>> It wouldn't help because it was a missing include file 
 BS>> in the CVS repostery.. I need to do a CVS checkout on 
 BS>> another dir, to check that I corrected all the errors.. 
 BS>> But sourceforge is a problem, because the correctings 
 BS>> is getting on 24 hours later :(

 BJ> Ah....  Sometimes when I'm making this type of update, I'll download 
 BJ> from sourceforge into a clean directory and attempt a recompile to 
 BJ> check for this type of thing....  Yes, that takes added time.....

Indeed, I did so before sourceforge got the 24 hour problem.

 BJ>> I know, sometimes that isn't convientent that something
 BJ>> broke at that point in time, but we need to get in the habbit.....
 BJ>> And yes, we'll still miss things at times.....

 BS>> Let's hope sourceforge is getting better!

 BJ> I suspect they will keep development seperated from regular users due 
 BJ> to bandwidth issues......  Now, they might get the frequence of 
 BJ> updating the backup servers (that regular users access) 
 BJ> increased.....  At one point I saw something saying they wanted to 
 BJ> increase from once a day to four times a day (every six hours instead 
 BJ> of the original 24 hour update).....

It would be very nice if somebody could provide CVS access in the future so
we don't need to wait 24 hours to get defects in CVS corrected. I remember
with synchronet 1 minute after Digitalman corrected the error I could do a
CVS checkout, it was very nice!

Regards,
Bo

--- Msged/LNX 6.1.2