From: Alex Bennee Date: Wed, 15 Aug 2007 12:58:46 GMT Subject: Re: git-cvsexportcommit getting out of sync with CVS status requests Message-ID: <1187182726.13096.50.camel@murta.transitives.com> In-Reply-To: <1187178510.13096.46.camel@murta.transitives.com> On Wed, 2007-08-15 at 12:48 +0100, Alex Bennee wrote: > Hi, > > Occasionally (usually when a lot of files have been added or moved in my > git tree) git-cvsexportcommit gets confused when I'm exporting. I'll get > the error like: So I have figured out the reason it goes out of sync. CVS doesn't seem to always report status in the order you give it on the command line (which is rather crucial to the functioning of the script). e.g. cvs status path/to/filea path/to/filev path/to/filec can return the status in order fileb filea filec It looks like running a single CVS query for each file is the only solution. -- Alex Bennee - Alex.Bennee@transitive.com Behind every great computer sits a skinny little geek.