On Monday, March 13, "Christian Schmolzi" wrote:
> 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.
Don't do that. Use tags instead to mark which versions of a file you wish
to have included for each version of a project. Revision numbers are an
artifact, not a means to give something a definite version number...
--Toby.
