On 2011-07-12, STeve Andre' <and...@msu.edu> wrote: > I have seen this twice now in 4 months, where getting a new tree > was the solution. Next time this happens I'm going to put the > suspect one away, and then compare it with the new (hopefully) > good one. > > If others who've crashed into CVS problems can shed light on > why this happens, I'd be all ears.......
Don't know if it might be the case here, but I would be very wary of switching between an anoncvs server running gnu cvs and one running opencvs. "cvs -d $CVSROOT version" will show you what it's running.
