If I am not mistaken, you are trying to use the rcs version numbers as file version numbers (in windows you can see this info by <right click>->properties->details). The number should not be the same as rcs version numbers because they where not designed (as you can see) to be used externally. The best way to handle this is to create a new versioning scheme that maps publicly visible version numbers to rcs version numbers. The functionality would be the same as tags and branches in cvs.
So for release 1.0.1 of your product, you have a map that says 1.0.1 contains rcs version 2.0.3.1.0.1.76 for file a.txt and 1.6.0.1.1.0.2 for b.txt. (Just like a tag REP_1_0_1 would 'point' to the same rcs revision numbers in cvs.) Alternately on a file level you can map like so: a.txt v1.0.2 maps to 2.0.3.1.0.1.76 b.txt v2.0.3 maps to 1.6.0.1.1.0.2 ** where the vX.X.X numbsers are visible to the customer. You can use a combination of these methods. It is more work on your end. But the version numbers are nicer for the customer and your support team. Regards, --Russ _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
