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
Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
Date
Aug 15, 2007, 15:53 UTC
Message-ID
<46C3218E.6020309@fs.ei.tum.de>
In-Reply-To
<1187182726.13096.50.camel@murta.transitives.com>
Alex Bennee wrote:
> It looks like running a single CVS query for each file is the only
> solution.
I think internally CVS is doing single queries anyways.  At least that was my impression.
Or we find out which order cvs is reporting the status.  Maybe a simple sort of the pathnames could be sufficient?
cheers
  simon
Previous: Alex BenneeNext: Johannes Schindelin
Message 3 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.