Re: [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file.

"Martin Langhoff" [off-list ref] writes:

On 5/10/07, Steffen Prohaska [off-list ref] wrote:

quoted

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,

Sounds like you are perfect guinea pig.  A test in the real-life
use followed by an Ack is very appreciated.