started @ 10:56 PM on 10/9/07

10:57 PM: "CVS (Concurrent Versions System) is a tool that enables you to track changes to a set of files over time. CVS is commonly used in software development to allow multiple developers to coordinate changes, track versions, and permit simultaneous development of different versions of the same code."

11:10 PM: "One family I know uses CVS to store their shopping list, to keep them from overwriting each other's entries." NERDDDSSSS!!

11:14 PM: creating a CVS project...


/tmp$ mkdir example
/tmp$ touch example/file1
/tmp$ touch example/file2
/tmp$ cd example
/tmp/example$ cvs -d /var/lib/cvsroot import example example_project ver_0-1


11:16 PM: checking out 

$ mkdir ~/cvs
$ cd ~/cvs
$ cvs -d /var/lib/cvsroot checkout example

11:16 PM: committing changes

$ cd ~/cvs/example
$ cvs commit

11:18 PM: good tips:


Synchronize the clocks of computers sharing a repository to the same universal time. CVS relies on file timestamps to determine which files have changed.

Give each developer his own sandbox, and communicate all file changes through CVS. This maintains change tracking and prevents developers from irretrievably overwriting each other's work.

Update frequently, at least before starting work every day, to keep your sandbox current.

Commit frequently to keep your repository current. Programmers typically update every time their code compiles cleanly; other people may commit after completing each block of work.

Programming teams: use build-management tools and ensure that all files in the build are committed to the repository. Ensure that builds for testing or release come from the repository rather than a sandbox, but allow sandbox builds for programmers to do pre-alpha tests.

12:27 AM: "The default port for kserver is 1999."

done @ 12:43 AM on 10/10/07