git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-cvsexportcommit getting out of sync with CVS status requests

From
ABAlex Bennee <alex.bennee@transitive.com>
Date
Aug 15, 2007, 12:58 UTC
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:
Show 5 quoted lines
> 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.
Previous: Alex BenneeNext: Simon 'corecode' Schubert
Message 2 of 5 in “git-cvsexportcommit getting out of sync with CVS status requests”
  1. Alex BenneeAug 15, 2007
  2. Alex BenneeAug 15, 2007
  3. Simon 'corecode' SchubertAug 15, 2007
  4. Johannes SchindelinAug 15, 2007
  5. Simon 'corecode' SchubertAug 15, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.