[cvsnt] Cvs commit in batches of 1000

McCullough, Ryan rmccullough at rightnow.com
Thu Nov 3 21:50:43 GMT 2005


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.


Dang, I appologize. I keep hitting just a ctrl-r and it replies to the
person instead of the list.

CLIENT
C:\>cvs ver
Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build 2088
(client/server)

SERVER
[cvs at bighorn cvs]$ cvs ver
Concurrent Versions System (CVS) 1.11.17 (client/server)

And I have to admit that I am running
cvsspam(http://www.badgers-in-foil.co.uk/projects/cvsspam/) on the cvs
server. I kind of need this too, its how my manager gets notified of the
changes to everyones scripts that day.


-Ryan

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Bo Berglund
Sent: Thursday, November 03, 2005 1:05 PM
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: Re: [cvsnt] Cvs commit in batches of 1000

On Thu, 3 Nov 2005 11:02:36 -0700, "McCullough, Ryan"
<rmccullough at rightnow.com> wrote:

>From a *private* reply email (please do send responses to the list
instead of directly to me...):
.. snip ...
>What my script does is checkout the module into ./scripts. Under 
>./scripts is a directory which matches the username, we will use john.
>Now, once the directory is checked out, I copy over the scripts, vp's 
>and low-level recorded files into my cvs sandbox. I will then do about 
>6 'cvs add' commands to pick up new files. Then I run one large commit 
>command. Here is the command line:
>
>cvs -z3 commit -m "John - Automation daily checkin - 11/03/2005"
>
>This command returns:
>cvs commit: Examining .
>cvs commit: Examining lls
>cvs commit: Examining vp
>Protocol error: too many arguments
>
>I am going to experiment with using the -c option to the command line 
>but from my understanding cvs should automatically only try to commit 
>changed and new files right? So the -c option is kind of a moot point.
>Additionally, it is only occassionally that there are enough changed 
>files that the import fails.

The only way I can figure out is that behind the scenes (without
feedback to the user) cvs is executing a shell command or similar with a
command line consisting of a list of files to commit and this list gets
way too long.

Now it is very important that you tell us what version you are running.
This is best done by executing the 'cvs ver' command from within a
sandbox and pasting the result back here.


/Bo
(Bo Berglund, developer in Sweden)
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs




More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook