From: Martin Langhoff Date: Thu, 10 May 2007 06:53:51 GMT Subject: Re: [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file. Message-ID: <46a038f90705092353x107c738foa7db547ab29b1748@mail.gmail.com> In-Reply-To: <380B28A3-5CD0-4371-A717-1D2629E6302D@zib.de> On 5/10/07, Steffen Prohaska wrote: > I'll post a patch soon that takes the best of both: Call cvs status > once with the list of touched files and parse the output. Only one > connection is needed and only the minimal amount of status data is > transferred. Yes, please :-) I wrote cvsexportcommit originally, and use it on a huge cvs checkout that is hosted on SF.net (slow!). My commits are small (3~5 files). I agree with using only one connection so commits with many files are sanity-checked faster, but status needs to ask explicitly about the files it's about to touch. cheers, m