An introduction to CVS

CVS is the version control system we (well, some of us) use around the ILRT. It manages source code and other projects that fit into the text-document mold.

It's pretty straightforward, once you get to grips with it, but the "getting to grips with" can sometimes prove problematical.

I'm offering a short session introducing the command-line tools for CVS for those who've not seen it before: the target audience is technical developers who haven't used CVS before.

Prerequisites will be some familiarity with a unix command line, a unix account, and I'll need names beforehand so that we can set up access to the repository for people. I'm not going to go into advanced esoterica but I might run a followup later on if it proves popular.

Because the introduction has to be practical, there's a maximum limit of 6 people for this.

I'll also try to present some guidelines about how to get the most out of CVS (a "CVS patterns" guide, if you will).

Prerequisites - please read

The following are things you need to check or do prior to turning up for the session. Please, please get in touch with me on or before the 4th July 2003 if you are having trouble with any of these.

Once you've done this, you're ready to go. I'm sorry if this list seems daunting, but if everyone is going to get the most benefit out of the session I'd like to get the debugging done prior to the day.

What we'll cover on the day

The following are pretty much what I'm intending to cover. This should run to no more than a couple of hours (depending on how fast we whizz through it) including time for coffee in the middle. I'm going to concentrate on the hands-on aspects rather than the theory.

Questions are invited at any time.

What I'm not going to cover