Re: revision number less than 1.1

[Kaz Kylheku]

In article <address@hidden>, Petr Aubrecht wrote:
>Hello,
>
>I started to use CVS and have one small trouble.
>
>I would like to use revision numbers less than 1.1, let say 0.0.1, or 1.0.1
>etc.

Why, are you superstitious about numbers? 

You can't use these numbers, because zeros are special. In CVS,
a number matching the pattern *.0.* is a ``magic branch number''.

Really, people should stay away from these numbers completely and
just use tags to identify code baselines.

The numbers are sometimes useful if you have to debug some problem, or
do some operation on an individual file, such as undoing specific changes.

>It allows me to make the revision number the version number of the
>software (is it bad idea?). Now, cvs commit -r 0.1 doesn't work.

The version numbers in CVS have nothing to do with the version number
of your software. Forget about it.

>Is there also a way how to store all histories at once? I would like to see
>what has changed in all project, not for single file.

The only way to do that currently is to use some clever programs
that can post-filter the output of cvs log, to rearrange the information
differently. For example Karl Fogel's cvs2cl.pl script can reconstruct
a ChangeLog from a module's history, by recombining the commit histories
of individual files.