Any technical issues with CVS long version numbers?

Question

Our project has a history of creating new branches in CVS from existing branches. After several years, this led to this situation in the files that were changed in each release:

new edition: 1.145.4.11.2.20.2.6.2.20.2.1.2.11.2.3.2.4.4.4.2.5.2.1.2.1.2.6.2.23,
previous edition: 1.145.4.11.2.20.2.6.2.20.2.1.2.11. 2.3.2.4.4.4.2.5.2.1.2.1.2.6.2.22

Obviously this looks bad in the CVS console, but does it really matter technically? Did we get anything by combining everything back to the head to get back to 1.146?

(PS "Switching to Subversion" is not the answer.)

Answer 1

, , , , . , ; , , , . ( , . • P)

-, , 1.146?

. , . , 1.146? , , , , .

Answer 2

-, , 1.146?

:

• . , . CVS , , .

• . , CVS deltas, HEAD (. rcsfile (5)). , CVS, , HEAD.

• . , - , (CVS? Commit notification tools? Web viewer? IDE-?) , . , , .

, :

• , CVS , , "" . , cvs log , .

• , , . ( , , .)

• ( , ), CVS , ( ), , .

, , , HEAD.

Answer 3

CVS, , CVS, . . , 50 100, . , , , ​​ , .

, . , , .

: , , , . [ ]

, 4 5 max. , TOO LONG . 4 5 ,

: < > . < semi major release > . < > < > , - 4.2.12.45, 4 ( , ), , 4, - , 4, 12- , .. , , 45- 4.2.12. , - .