CVS revision numbers

When I execute the cvs status of my project, I get different version numbers for different files. What's going on here? Do all files have the same version number?

+6
version-control cvs
source share
4 answers

The CVS version number indicates how many times this file has been modified. If you need something consistent in the project, you will need to use the cvs tag after you have done all the agreed label.

+9
source share

not. cvs does not have a single revision number, like more modern version control systems. Each file has its own separate version. If there is any way, you can switch to another version control system like subversion, mercurial, git ... do it.

+6
source share

CVS does not have global revision numbers; they are per-file. (Actually, CVS doesn't even have atomic commits)

+1
source share

CVS was originally a set of scripts over file RCS, and it never escaped its history. The CVS repository is a collection of RCS files located in the directory structure that you want when it selects, as well as some lock directories. Remember this, and you will understand (and perhaps be able to anticipate) a lot of CVS idiosyncrasies. (Later, VCS came up with the idea of ​​creating directories, as well as things like file continuity in all renames.)

The idea of ​​CVS global state is a tag that must be applied manually. This is done by tagging each RCS file. It is also possible to get a copy of the repository at a given point in time, but this is not necessarily agreed, since large commits are not necessarily atomic.

So no, the CVS version of the file is the RCS version in the repository and has nothing to do with any other revision number. Do not sweat revision numbers.

+1
source share

All Articles