Sam Steingold wrote: > > I have a file foo at revision 1.1234. > It was extensively modified and committed as 1.1235. > I wish it were committed as 2.0 instead. > What are my options? > > All I can think of at the moment is: > > 1. cvs admin -o 1.1235 foo > 2. edit CVS/Entries > 3. cvs ci -r 2.0 foo > > is there a better way? > > in particular, DIUC that "cvs ci -r 2.0 foo" will _add_ a revision 2.0 > on top of 1.1235 (not replace 1.1235 with 2.0)? > > (I know about tags, and I do not wish to use them here. > All I want is to change the revision number, that is all. > I am not interested in branching &c &c) > > Thanks. 1. UM, if I read the help right that will DELETE the specified version. 2. Don't think that will work. 3. that might work.
Note that there are some assumptions that CVS makes about version numbers and hand tweaking them as you are suggesting has implications later on. the usual suggestion is to remember revision numbers are something only cvs should be looking at, if you want something for a human to look at apply a tag. see the following threads for some of the problems that can be caused by forcing a version: http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=revision+2.0&submit=Search%21&idxname=info-cvs&max=20&result=normal&sort=score http://lists.gnu.org/archive/html/info-cvs/2002-06/msg00013.html http://lists.gnu.org/archive/html/info-cvs/2004-12/msg00162.html http://lists.gnu.org/archive/html/info-cvs/2003-05/msg00065.html -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
