Hi Pierre-Luc Deweerdt,
>I'm currently using WinCVS 1.0.6 on Windows NT ... For some strange
>reason, since i changed my local working directory, win CVS eats up to
>50-60%
>of my CPU time, which he didn't do before ... Is that a current
>troubleshooting
>or is it unusual ?
>Do you have any solution or answer to that problem?
It could be caused by WinCVs monitoring the changes in the directory, are
you doing something in the same directory that WinCVs points to, like
compilation/build etc.? You should consider the upgrade to the new version
of WinCvs and see if the problem will be gone... I tried the compilations
and WinCvs pointing to the same directory - it took no more that 15% for
WinCvs, most of time it was below 5%. I am using WinCvs 1.1b7 on NT.
Good luck,
BR,
Jerzy
The first thing they don't teach you at school: "Never say never".
All the issues not related to the list please send to me in private, thanks.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com