This is way off topic, but I'll try. I'm trying to understand CVS. I've got the repository setup on the same machine I'm developing on so it's ready to go. I'm the only developer on this project, so I'm just using CVS for my own version control and too keep track of the state the software was in when it was installed on other machines. I have read 'info cvs', yet, but it hasn't soaked in yet, I'm afraid. Too much fun in my youth, perhaps. I'm really more curious how people use it day-to-day while developing, and then the process used to update some "live" site. Say I've got a CGI application that I'm working on with the following directory structure. ~/project_one/ cgi-bin <-- want under cvs control template <-- cvs, too config <-- cvs, too data <-- Don't want under CVS Here are my questions: 1) How do I put this project under CVS control? I don't want the data directory placed in CVS, which is very large. 2) and I'm unclear how to group all those directories as a single project under CVS. That is, how do I checkout a file from ~/project_one/cgi-bin and not from ~/project_two/cgi-bin. Yet, I don't want to have to checkout/checkin the entire project each time I make an update. 3) What is the checkout and checkin procedure? - Can I checkout just the cgi-bin directory? - Can I checkout just one file in one directory? 4) I have a "live" site running this project on a remote machine. On the remote machine I have two copies of the files: one for testing, and another for the "live" files. Is CVS a good way to move files from the repository to the live machine? Is this also a "checkout" or is there another way to move files? 4a) And, is there a way to do a remote checkout over SSH? Finally, I'd be curious on the general way people use CVS when developing. How often you checkin and such. Thanks, Bill Moseley mailto:moseley@hank.org -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/