Menu
▾
▴
#932 External Diff Hangs
When I try and do an external diff with an older
version of a file, using either the graph or manually
specifying a revision number, wincvs outputs the following:
cvs update -p -r 1.1.2.8 -- ResWareSchemaFNAS.DDL (in
directory C:\SandBox\ResWareHead\ResWareSQL\)
===================================================================
Checking out ResWareSchemaFNAS.DDL
RCS: /devel/cvs/ResWareSQL/Attic/ResWareSchemaFNAS.DDL,v
VERS: 1.1.2.8
***************
and does nothing but cycle fishes. If I then press stop
I get the following output:
cvs [update aborted]: received interrupt signal
***** CVS exited normally with code 1 *****
cvs diff -r 1.1.2.8 -- ResWareSchemaFNAS.DDL (in
directory C:\SandBox\ResWareHead\ResWareSQL\)
Index: ResWareSchemaFNAS.DDL
===================================================================
RCS file:
/devel/cvs/ResWareSQL/Attic/ResWareSchemaFNAS.DDL,v
retrieving revision 1.1.2.8
retrieving revision 1.1.2.9
diff -r1.1.2.8 -r1.1.2.9
and a normal diff is outputted to the window.
This does not happen for all files, and seems to work
for files that have changes but have not been checked
in when compared against the last checked in version.
It used to work fine, then today this behavior started
occuring.
Internal diff works fine.
I'm using 2.0.2.4 build 4.
Logged In: YES
user_id=119527
Can't reproduce - we need the exact pattern but it looks
like perhaps something locally on your machine
Logged In: YES
user_id=1127198
I've noticed if this happens and wincvs is in the hung state
and I go into task manager and kill cvs.exe, that things
proceed to work fine.
Adam
Logged In: YES
user_id=158827
Please specify type and version information about your
CVS/CVSNT client and server binaries and consider retesting
with a different build on either end to see if that fixes
the problem. To me this sounds more like CVS/CVSNT issue
rather than a WinCvs issue if the cvs.exe is hanging...
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 30 days (the time period specified by
the administrator of this Tracker).