Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

Software Configuration Management versioning approach

Status
Not open for further replies.
L

LOSTISLAND

Member level 3
Joined
Jun 8, 2010
Messages
54
Helped
6
Reputation
12
Reaction score
5
Trophy points
1,288
Activity points
1,682
Hi all ,

By default, when you check in a file, Source Integrity and PVCS automatically assigns a unique revision number to the new revision. It does this by incrementing the current revision number by one. For example, if the previous revision is 1.3, the new revision is assigned number 1.4.
But Some Software Configuration Management Tools Like Perforce and TortoiseSVN , use an integer number for every check in or commit .
For example, if the previous revision is 13, the new revision is assigned number 14.

Are there any other Tools which use Source Integrity or PVCS like convention ?

Thanks in advanced
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top