Basic CVS and WinCVS Concepts
When working with CVS, there are several concepts that you should know:
When working with CVS, there are several concepts that you should know:
These are the tasks you'll need to perform to get started with WinCVS:
You can download the latest version of WinCVS from it's Internet home, wincvs.org.
The other day someone not familiar with CVS asked if they could have a copy of the source code for the DDConnectionBroker project, an Open Source project from DevDaily.com. I said sure, I'd be glad to provide a copy of the source code, stripped of all the CVS directories/files. To do this, all I had to do was run the "cvs export
" command.
Just returned from a short trip to the northern outskirts of Chicago, Illinois. Wow, can it rain.
On the computer side of life, have you ever found yourself needing a copy of the stuff (source code, etc.) in a CVS repository, without all the CVS admin files? Here's a quick tutorial on how to use the cvs export
command.
After my memory failed me again, I modified this CVS tip on how to set the CVSROOT for a CVS server and log in to CVS using the "cvs login" command from the good old command line.
CVS login FAQ: How do I login to a CVS server using SSH?
Here's how I do a "cvs login" to our CVS server using SSH, on a Windows PC:
set CVSROOT=:ssh:al@some.server.com:/home/cvs/ cvs login
Note that the only real different thing here is that you specify the ssh protocol for communicating with the server.
This section assumes that that you've already checked out a project from a CVS repository and you're ready to start working on it. This section is broken down into the sub-sections:
I started to write about a few "special CVS tasks" that a user needs to perform from time to time, but as a practical matter, I've found that most new users don't need to worry about tagging a release for at least a little while, so I've skipped this topic here, at least for the time being.