[cvsnt] Re: Cvs commit in batches of 1000
bo.berglund at telia.com
Thu Nov 3 18:01:11 GMT 2005
On Thu, 3 Nov 2005 10:00:32 -0700, "McCullough, Ryan"
<rmccullough at rightnow.com> wrote:
>Is there a way to do a 'cvs commit' but have it commit files in
>batches of 1000 files? I am running into problems trying to commit
>several thousand files and it exceeds the maximum number of options.
Do you have more than 1000 edited files in a single directory???
Sounds weird, normally one edits a few files and then commit and this
will not cause a congestion. Simply cvs commit -m"message text" is
If you have all of these files do you really list them on your command
line, i.e. are you making a slection from a much larger set of edited
files? I don't understand how you can even get close to the number of
modified files you mention.
Just a thought experiment:
- Editing a file means thinking up some changes, opening the file in a
suitable editor, entering the changes and saving the file. I doubt
that all of this can be done in much less than say 5 minutes on
average, but let's assume warp speed editing so you get 1 minute per
- 1000 minutes adds up to nearly 17 hours of constant editing files
So as I said, how can you get even close to 1000 edited files between
commits? You should commit as soon as you have done some few sensible
edits and not leave it all to commit your last few months worth of
But then again I may completely misunderstand your situation...
(Bo Berglund, developer in Sweden)
More information about the cvsnt