News
	Latest
	Archive
	Community news

Articles
	C++
	Communities and Content
	Databases
	Editorials
	Emacs
	General
	HTML
	Java
	Notices
	PHP
	XML

Links
	Apache
	C++
	Database
	General
	HTML
	Java
	Javascript
	Linux
	Object oriented programming
	Open source
	Perl
	PHP
	Python
	Ruby
	SOAP
	XML
	Suggest a link

About
	Advertise on zez
	Contribute
	Contact us
	About zez

Version Control management with CVS - Part 2

Author: Jan Borsodi

Publishing date: 24.11.2000 11:33

Version numbers

You might have noticed when working with a CVS repository that each file has a given number. For instance it might have 1.0, 1.2 or 1.8, the number is what's commonly called a revision number, which gives the user a clue on how many times the file has been modified. Files which are frequently modified will have high numbers, for instance 1.50.
Revision numbers are not be confused with program version. A program with version 1.4.2 might have files with varying revision numbers.

A version number will always have an even number of period-separated decimal integers. So a revision number of 1.3.2.2.4.5 is allowed. Revision 1.1 is by default the first version of a file. When revision numbers have more than one period it is part of a branch, branches will be explained in a later part. Normally there's no reason to care about revision numbers as CVS will automatically increase them internally. However sometimes you might want to change the revision on all your files when you have released major version of your software.
Note that using tags, which will be explained in a later part, is a much better way to handle releases.

So if you wanted all files to have a new revision number you would use the commit command with an option. For instance

cvs commit -r 3.0

will bring all your files up to revision 3.0. Revision numbers can only be increased, so trying to set a revision number of 1.3 when other files have revision 1.5 will fail.

<< Previous page | 1 | 2 | 3 | < 4 > | 5 | Next page >> | Printer-friendly page |

Comment List

Topic:	Author:	Time:
regexps are supported	Marius Sundbakken	26.11.2000 05:23
When commiting changes, it is often necessary to commit both the header file and the source file, and conveniently, cvs support: cvs commit foobar.*
RE: regexps are supported	Jan Ekholm	27.11.2000 10:57
> When commiting changes, it is often necessary to commit both the header file and the source file, and conveniently, cvs support: > > cvs commit foobar.* Isn't this expanded by the shell? CVS just gets the expanded list, such as: cvs commit foobar.h foobar.cpp Or am I out in thw woods here?
RE: RE: regexps are supported	Michael Krumpus	27.11.2000 15:40
> > When commiting changes, it is often necessary to commit both the header file and the source file, and conveniently, cvs support: > > > > cvs commit foobar.* > > Isn't this expanded by the shell? CVS just gets the expanded list, such as: > > cvs commit foobar.h foobar.cpp > > Or am I out in thw woods here? You are correct. The shell handles this, not CVS (or any other program).