I did some googling and couldn't really find any helpful info on this, so I'm 
posting here.

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?

Most of the time is just passing through directories, doing nothing. Do you 
tag the working part of the code and just work there? Only cvs update the 
whole thing every week?

All ideas are welcome :-)
-- 
Bob Tanner <tanner at mn-linux.org>          | Phone : (952)943-8700
http://www.mn-linux.org, Minnesota, Linux | Fax   : (952)943-8500
http://www.linuxjustworks.com             | Linux Just Works!         
Key fingerprint = AB15 0BDF BCDE 4369 5B42  1973 7CF1 A709 2CC1 B288

_______________________________________________
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