Yeah, I'm coming around to Recon's opinion - the constant updating is bad. I'm not for locking down to one revision and staying with it FOREVAH, but we should work "update to the latest CS rev" into the milestones, and only do it when we know the current code base works; this way, we can track down issues related to updating CS without having them clutter up the other "durr, forgot to increment the pointer" kinda bugs.