This is like informing the library of what changes she made to the book and why.The library then incorporates these changes into a "master" copy, where they are recorded for all time.The developer can simply say, in effect, "Give me the program as it was three weeks ago", or perhaps "Give me the program as it was at the time of our last public release".
The remainder of that book - chapters 1, 3, 5, and 7 - deals with the challenges and philosophical issues of running an Open Source project using CVS. These chapters are released under the GNU General Public License.While the free chapters here constitute a complete CVS book by themselves, we certainly hope you'll like them enough to purchase a treeware copy of the entire book! For more information about free software in general, visit and particularly To debug the problem (which may also exist in the current version of the sources), the program has to be brought back to a useable state.Restoring the state poses no difficulty if the source code history is kept under CVS.) As far as CVS is concerned, all developers on a project are equal.
Deciding when to update or when to commit is largely a matter of personal preference or project policy.It is part of a larger work entitled This is a set of free, online chapters about using CVS (Concurrent Versions System) for collaboration and version control.It covers everything from CVS installation and basic concepts all the way to advanced usage and administration.This document is free software; you can redistribute and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version.This document is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.If you've never used CVS (or any version control system) before, it's easy to get tripped up by some of its underlying assumptions.