The problem you just described is why you should totally ignore the CVS revision numbers and use tags instead to mark different states or releases of your software. Make tag names like "Release-2-0", "Release-2-1", and "Release-3-0", for releases 2.0, 2.1, and 3.0, respectively. Also, document the tag names in a text file you keep with your source code so you can find and understand the tag names when you need them. Tags are a very powerful for marking code, tracking changes, etc., and are required for using branches (another powerful CVS feature). Use the tags - you'll be glad you did. Trust me. Alan Thompson "Christian Schmolzi" <[EMAIL PROTECTED]> on 03/13/2000 09:08:24 AM To: [EMAIL PROTECTED] cc: (bcc: Alan Thompson/Orincon) Subject: Assigning revision numbers I have a problem assigning revision numbers to our project files. After releasing version 1 of our product we decided to assign a revision number 2.0 to all files. I did this with "cvs commit -r 2.0" which worked quite ok (a few files have not been touched an remained 1.x but I am able to fix this by hand. The problem is: when I add a new file in a directory where files with revision 2.x exist, this new file gets revision 1.1 instead of 2.1 as mentioned in the manual. How can this happen? I understand there should be a file called "Tag" in the CVS subdirectory in each project directory but there isn
�t. We use cvs version 1.10.2 but I tried it with 1.10.8 and the problem was the same. Can somebody help me? I can supply more information about the files in CVSROOT if you need it. Ciao, Christian
