I have searched on Google, Some one gives a reasonable answer.
I should unset HOME varible before restart xinet.
But after I do it, it seems still exist. And I used found that
rebooting can fix it, but it is proved later that this bug is still
there.
And many people has also encounter this
yes, some analysis of this problem is here.
https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_21.html#SEC189
After I updated to version 1.11.19, the error report still exist.
And I fixed it by special -f in xinet startup file for cvs.
The following is some details:
The article has introduced
ypi can use wincvs or other GUI front to help you.
If you are not very familiar with the command line opition, and the
operation.
Enjoy.
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
