Bob Tanner writes: > When your cvs repository gets large enough that a cvs update -dP > takes 15mins, and cvs commit at just as long, what do you do? http://www.bitkeeper.com/ CVS is not very efficient and has a lot of deficiencies (like no renames). Buying a better source management system such as BitKeeper might be worth your while: http://www.bitkeeper.com/Products.Comparisons.CVS.html Other than that, your best bet is to split up your repository into multiple repositories. Chances are, you don't need everything in one repository. If you do, then you either need re-evaluate your development practices, or you are developing something so large that you should be looking at a better source management system. OT: If you want to look at new free revision control system that is very cool, check out darcs: http://abridgegame.org/darcs/ -- David Phillips <david at acz.org> http://david.acz.org/ _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list