Re: version numbering

[Aaron S. Hawley]

Hey Balbir,

I too recall trying to force RCS to mimic its revision numbering system
with the version numbering system I desired.  Unfornutately, in RCS the
trunk revisions must be started with the form of 1.3, and branches of
1.3.1.1.  The purpose of the revision numbering system is to match the
revision making process, not the version numbering system of software
releases.

For more on revision numbering see rcsintro(1):

 $ man rcsintro

Fortunately, RCS gives the -n (and -N) option as an alternative for
logging version number information.  See rcs(1) for more info.

If you have a trunk revision numbered 1.3, you could do this for releasing
version 1.3.0:

 $ ci -nPabla_1_3_0 -f1.3.0.1 -tdescription.txt *.ftn90 <log.txt

and this for creating version 1.3.1:

 $ ci -nPabla_1_3_1 1.3.1.1 -tdescription.txt *.ftn90 <log.txt

/a

On Thu, 27 Oct 2005, Pabla,Balbir [Ontario] wrote:

> Hi :
>
> I want to check in my source code starting from numbering 1.3.0 and then
> the next version 1.3.1 in a separate directory.
> As long as I use 1.3, it works, but not 1.3.0.
> Please note that I don't want to use any branch, it is all trunk in the
> same line.
>
>  Ci -f1.3.0 -tdescription_file.txt *.ftn90 <logmessage_file.txt  ..it
> says that branch point does not exist for revision 1.3.0.
>
> Please note that I don't want branches, in fact 1.3.0 is my starting
> point.
>
> So my question is that how  can I start my numbering from 1.3.0
> instead of 1.3?
>
> Thanks
> B. Pabla
> address@hidden