From: Steffen Prohaska <prohaska@zib.de>
Date: Wed, 09 May 2007 13:00:50 GMT
Subject: Re: [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file.
Message-ID: <3467FF99-9945-4ECF-9282-308759E63ED9@zib.de>
In-Reply-To: <Pine.LNX.4.64.0705091424190.4167@racer.site>


On May 9, 2007, at 2:25 PM, Johannes Schindelin wrote:

> What I was trying to get at: if you commit 900 files, and after the  
> 450th
> file somebody _else_ commits a file, which just so happens to be  
> one of
> your 450 remaining files, that safety check no longer holds.
>
> CVS is slow.

I know. I'd probably apply my patch late at night or on the weekend,  
when the chance is lower to conflict with other commits.

You can't remove the race conditions that you have when interacting  
with cvs. We can only decrease the chance of being hit by making the  
time window smaller. This is a side benefit of my patch. The main  
purpose is to lower the overall time needed to apply patch that  
modifies lots of files.

- Steffen