[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Latest Stable Branch & Windows - Odd Messages
From: |
Conrad T. Pino |
Subject: |
RE: Latest Stable Branch & Windows - Odd Messages |
Date: |
Sat, 24 Sep 2005 12:20:57 -0700 |
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: bug-cvs-bounces+conrad=pino.com@nongnu.org
> [mailto:bug-cvs-bounces+conrad=pino.com@nongnu.org]On 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