Let's start with a very simple case: H:\cvs-1.11>set CVS_CLIENT_LOG=U:\cvslog
H:\cvs-1.11>windebug\cvs status ChangeLog =================================================================== File: ChangeLog Status: Up-to-date Working revision: 1.692.2.225 Repository revision: 1.692.2.225 /cvsroot/cvs/ccvs/ChangeLog,v Sticky Tag: cvs1-11-x-branch (branch: 1.692.2) Sticky Date: (none) Sticky Options: (none) Unable to write to standard output H:\cvs-1.11> > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Derek > Price > Sent: Saturday, September 24, 2005 11:11 > To: Conrad T. Pino > Cc: Bug-non-GNU CVS > Subject: Re: Latest Stable Branch & Windows - Odd Messages > > This error usually means that the client thinks it is done processing > but the server is still sending data. You might try setting > CVS_CLIENT_LOG in the environment to a path to a file and use that file > to examine what your client and server sent to confuse each other. > > Regards, > > Derek
_______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
