Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Mon, 18 Aug 2003 13:29:56 -0700, "Lawson.Reed" <Reed.Lawson at IGT.com> wrote: >> -----Original Message----- >> From: Aaron Kynaston [mailto:akynaston at novell.com] >> Sent: Monday, August 18, 2003 12:44 PM >> To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook; Lawson.Reed >> Subject: RE: [cvsnt] The command line is too long. >> >> Alexandre just asked what versions you're using . .I'd like to hear >> that too. > >Sorry. Should have stated that in the beginning.... >WinCvs 1.3.13.3 beta 13 build 1 >CVSNT: 2.0.2 (shipped with above) > >Thanks, >- Reed. If you are using WinCvs then what you see in the command window is a shortened version of the real command sent. And if you have selected files in the files pane when you click Commit, then each and every one of these files will be individually listed on the command line to cvs. If you select a folder in the folders pane there will not be any files listed at all. Worse still, if you have enabled flat view when you do this I think that the command line gets even longer. So the command line stretches the capacity of Windows to the limit already for cvs.exe, even when the scripts are fixed. By the way taginfo was fixed long ago, before the 2.0.x releases, loginfo I don't really know though. But I am not sure it will help at all if you use WinCvs to throw too much at cvs at a time. /Bo (Bo Berglund, developer in Sweden)