[CVS] version number rules

CVS version tree ( Revision tree ) Can be divided into different branches ( Branches ), Each branch can be an independent self-maintenance development line. Changes in a branch can be easily moved back to the trunk.

Each branch has a branch number (Branch Number), Which is composed of an odd number separated by "." In decimal format. Append an integer to the version number separated by the corresponding branch to create the branch number. You can use the branch number to separate multiple branches from a specific version. WhenCVSWhen creating a branch number, it takes an unused even integer and starts with 2. In this way, when you want to create a branch from version 6.4, the branch number will be 6.4.2. All branch numbers ending with zero (for example, 6.4.0) areCVSInternal use. (Branch 1.1.1 has a special meaning)
In this case, we use
CVS log-t-r branch name file name
A strange phenomenon occurs when you view a file,

Code
Working file: goldequip.txt
Head: 1.63
Branch:
Locks: strict
Access list:
Symbolic names:
Tag_issue_v_247_20090806: 1.4 . 6.1 . 2.12 . 2.21 . 12.2
Tag_issue_v_04_253_20090806: 1.58 . 16.1 . 2.1
Tag_issue_v_03_00_269_20090804: 1.4 . 6.11 . 2.4 . 2.1 . 22.3
Tag_issue_v_246_20090803: 1.4 . 6.1 . 2.12 . 2.21 . 12.2
Tag_issue_v_245_20090730: 1.4 . 6.1 . 2.12 . 2.21 . 12.2
Tag_issue_v_04_251_20090730: 1.58 . 16.1 . 2.1
Tag_issue_v_04_250_20090728: 1.58 . 16.1
Tag_issue_v_243_20090723: 1.4 . 6.1 . 2.12 . 2.21
Tag_issue_v_04_248_20090723: 1.58 . 16.1
Tag_issue_v_00_000_038_20090723: 1.4 . 6.11 . 2.4 . 2.1 . 12.1
Tag_issue_v_03_00_266_20090723: 1.4 . 6.11 . 2.4 . 2.1 . 22.3
Tag_issue_v_00_000_037_20090722: 1.4 . 6.11 . 2.4 . 2.1 . 12.1
Tag_issue_v_03_00_265_20090722: 1.4 . 6.11 . 2.4 . 2.1 . 22.3
Tag_issue_v_03_00_141_20090709: 1.4 . 6.1 . 2.25
Tag_issue_v_03_00_263_20090707: 1.4 . 6.11 . 2.4 . 2.1 . 22.3
Tag_issue_v_00_000_036_20090707: 1.4 . 6.11 . 2.4 . 2.1 . 12.1
Tag_issue_v_03_00_140_20090706: 1.4 . 6.1 . 2.25
Tag_issue_v_03_00_262_20090703: 1.4 . 6.11 . 2.4 . 2.1 . 22.3
Tag_issue_v_04_246_20090702: 1.58
Tag_issue_v_03_00_261_20090702: 1.4 . 6.11 . 2.4 . 2.1 . 22.3
Tag_issue_v_03_00_260_20090630: 1.4 . 6.11 . 2.4 . 2.1 . 22.3
Tag_issue_v_241_20090630: 1.4 . 6.1 . 2.12 . 2.21
Tag_issue_v_240_20090629: 1.4 . 6.1 . 2.12 . 2.21
Tag_issue_v_04_245_20090629: 1.58
Tag_issue_v_03_00_258_20090625: 1.4 . 6.11 . 2.4 . 2.1 . 22.3
Tag_issue_v_239_20090625: 1.4 . 6.1 . 2.12 . 2.21
B _dev_ib - 00 - 238_xia_20090624: 1.4 . 6.1 . 2.12 . 2.21 . 0.12
B _dev_cn - 06 - 244_junxia_20090624: 1.58 . 0.14
Keyword substitution: KV
Total revisions: 171 ; Selected revisions: 0
Description:
========================================================== ============================================

For example, if you create a branch B _dev_cn-06-244_junxia_20090624 Based on version 1.58, we see 1.58.0.14, but the client sees version 1.58. The revision content appears only after the first submission.

Keyword substitution: KV
Total revisions: 172; selected revisions: 1
Description:
----------------------------
Revision 1.58.14.1
Date: 2009/08/07 13:43:04; Author: ×××; State: EXP; lines: + 2-0; kopt: KV; commitid: 3a44a7bbee83c21; filename: goldequip.txt;
B _dev_cn-06-244_junxia_200906241.58.0.14
========================================================== ============================================

UseProgramCheck whether "CVS update-r branch name version number" is successful
CVS log-t-r branch name file name
1. Check whether revision exists. If not, 2
2. Check whether the symbolic names exists. In this case, only the new branch is created locally and has not been submitted. The version number of the above file is 1.58 when the new branch is obtained locally. After the first submission, it is 1.58.14.1.
3. Check the CVS status to check whether the local database is successfully obtained.

compared with the version numbers of the two files, the version numbers are meaningful only in the same branch. This means that if both files are submitted to the same branch, the first several segments must be the same. In theory, we should take out the last segment of numbers for comparison.
special cases: 1.19 and 1.18.2.2 are meaningless; 1.18 and 1.18.2.2 are meaningful