Dear Sir / Madam:
I encountered a problem when doing a commit. Hopefully there
is someone out there who has seen this before. Any help or
comment is appreciated.
We decided to bring the major revision number up to 3.1 so I did
a command:
cvs commit -m "Change major revision number." -r 3.1
The wierd thing is:
Some files are updated to 3.1, but there are files which still
stay at old version number. And I checked and there seems no
difference to me on files which work and files which don't work.
The actual error message is as following:
cvs [commit aborted]: there is no version here; do 'cvs checkout' first
The thing I don't understand is: when I did cvs commit before,
there never have problems or warnings. And it seems to me that
every file should have a version number? Why is that there are
files working and there are others which don't work, and they
are in the same directory and seems no different to me.
I am new to CVS world. I don't know if there is another way
to fix it. If there is another way to get around this, please
let me know.
Thank you.
Frank Pei
(408) 855-9988 ext 304
[EMAIL PROTECTED]
------------------------------------------------------------------------
Want to increase your website's income dramatically?
Join Chinese-dns.com Reseller Program Now!
Get USD22.00 per sale, go to http://www.chinese-dns.com
�Q�j�T�����������J�ܡS
��ˤ~����o�C���P��22�����������O�S
�֨� http://www.chinese-dns.com �u�W�ӽХ[�J������}���U���P�ӡC
