Ross Burton writes:
>
> Argh! The old files was version 2.2, so why is cvs not noticing and
> setting the version number to 2.3?
It's a bug in CVS (and yet another example of why you shouldn't mess
with the revision numbers). When resurrecting a file, CVS looks at the
major revision numbers of all the existing files in the same directory
and uses the highest one it finds for the resurrected file, but it
doesn't look at the resurrected file's revisions. In this case, it
appears that all the other files in the directory are revision 1.xxx, so
it's trying to commit the resurrected file at revision 1. You can work
around this by explicitly specifying revision 2 on the commit:
cvs commit -m "Re-arranged files" -r 2 absolute.oc
-Larry Jones
Don't you hate it when your boogers freeze? -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
