Jijo Thomas wrote, On 10/17/2007 02:53 AM:
I have a set of files in RCS. They have revision numbers of the form 116.xx.
Now, I need to migrate the ,v to CVS.
If I copy the ,v files from RCS repository to CVS repository, I'll have the
revisions of the file of the form 116.xx/
Now, I have a requirement that I need the revisions to have the form
10.xxinstead of
116.xx. How can I make this happen?
Please help.
I would point you to the specific FAQ entry[1] but ximibot has been acting a
little funky lately, so if that link does not work try going to the FAQ[2] and
searching for 'Is there a way to change the versions of files to 2.X?'.
Also in your case I think one of those undocumented assumptions you'll brake
is, CVS expects major (and minor) revision numbers to ALWAYS INCREASE.
I am beginning to think we need an rcs-to-cvs...UGH some one thought of it
before me[3]. we probably also need a cvs-to-cvs for those folks who
inherited a repository where someone made the mistake of using `cvs commit -r
2.1`. Of course we need versions of rcs-to-cvs and cvs-to-cvs that instead of
copying the ,v files, do checkouts and commits ala sccs2rcs[4] so that bad
choices of setting revision numbers get wiped out (make the assumption only
the TRUNK matters).
[1]
http://ximbiot.com/cvs/wiki/index.php?title=CVS_FAQ#Is_there_a_way_to_change_the_versions_of_files_to_2.X.3F
[2] http://ximbiot.com/cvs/wiki/CVS%20FAQ
[3]
http://cvs.savannah.nongnu.org/viewvc/ccvs/contrib/rcs-to-cvs.sh?root=cvs&view=log
[4]
http://cvs.savannah.nongnu.org/viewvc/ccvs/contrib/sccs2rcs.in?revision=1.9&root=cvs&view=markup
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
http://www.crane.navy.mil/custfeedback
