Re: Major revision numbers

[Larry Jones]

Krzysztof GORBIEL writes:
> 
> As I can read in CVS manual, new file added to a module should obtain major
> revision number eqal to the highest revision number in that directory (for
> example 2.1 if highest existing revision nubmer is 2.xx). Unfortunately it
> doesn't work. New file will have revision 1.1.

That depends on whether you're using local mode or client/server mode. 
In local mode (which is how CVS was originally designed), it works
exactly like the manual says.  In client/server mode (which was grafted
on after the fact, and after the CVS manual was written), only files
that are actually sent to the server are considered.  I've updated the
manual to note that fact.

> Have you any ideas how to create new files with the correct major revision
> number withour forcing it with commit oprions? Maybe there is a patch that
> will fix this problem?

The "correct" major revision number is whatever CVS chooses to assign --
revision numbers are for CVS's internal use, you should not care what
they are.  Use tags if you want meaningful information.

-Larry Jones

He just doesn't want to face up to the fact that I'll be
the life of every party. -- Calvin