csjava-developer

[csjava-developer] reversion rate issues

[<he...@sf...>]

HI, all! Also, how to change the reversion number to two digits? 



For example:



Now my current verision number after commited is 1.9, I want to go to 1.91
next time I commit, how to set that? I saw another guy have a version 1.29?
Can someone reset my version number to 1.01 and commit at a rate of 0.01? 

Thanks you for your help.



Henry Chan (Redjustice)

Re: [csjava-developer] reversion rate issues

[Toby D. <tj...@sf...>]

Lets not mess with the version numbers CVS assigns unless it solves a
*major* problem.

Toby


On 5/18/05 7:53 PM, "he...@sf..." <he...@sf...> wrote:

> 
> HI, all! Also, how to change the reversion number to two digits?
> 
> 
> 
> For example:
> 
> 
> 
> Now my current verision number after commited is 1.9, I want to go to 1.91
> next time I commit, how to set that? I saw another guy have a version 1.29?
> Can someone reset my version number to 1.01 and commit at a rate of 0.01?
> 
> Thanks you for your help.
> 
> 
> 
> Henry Chan (Redjustice)
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> _______________________________________________
> csjava-developer mailing list
> csj...@li...
> https://lists.sourceforge.net/lists/listinfo/csjava-developer
> 

-- 
Dr. Toby Donaldson
School of Computing Science
Simon Fraser University

Re: [csjava-developer] reversion rate issues

[Thomas J. <ntm...@gm...>]

On 5/18/05, he...@sf... <he...@sf...> wrote:
> HI, all! Also, how to change the reversion number to two digits?

CVS doesn't treat its revision numbers as decimals as one would
expect. Numbering goes as follows: ... 1.8, 1.9, 1.10, 1.11 ... 1.99,
1.100, 1.101 ... and so forth until someone decides that the major
version number needs to be changed to 2.x, which should only happen in
the (rare) case of major API changes that will cause older software to
break.