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

cvsps wierdness

From
Robin Rosenberg (list subscriber) <robin.rosenberg.lists@dewire.com>
Date
Jun 12, 2006, 20:47 UTC
Message-ID
<200606122247.02727.robin.rosenberg.lists@dewire.com>

I sometimes get out-of-order imports with git-cvsimport when consecutive commits have the same message. I narrowed it down to a small demo:

#!/bin/bash -x mkdir demo cd demo export CVSROOT=$(pwd)/cvsrepo mkdir $CVSROOT cvs init mkdir $CVSROOT/x cvs co -d sandbox x cd sandbox echo X >k.txt cvs add k.txtsometimes cvs commit -m "A commit" sleep 1 echo a >v.txt cvs add v.txt cvs commit -m "A commit" sleep 1 echo b >v.txt cvs commit -m "A commit" cvsps -x --norc

-- end --

The script creates a small CVS repo with three commits on two files. What's odd is that cvsps lists revision 1.2 of the file v.txt *before* version 1.1, like this:

---------------------
PatchSet 1
Date: 2006/06/13 00:34:15
Author: roro
Branch: HEAD
Tag: (none)
Log:
A commit
Members:
        k.txt:INITIAL->1.1
        v.txt:1.1->1.2
---------------------
PatchSet 2
Date: 2006/06/13 00:34:17
Author: roro
Branch: HEAD
Tag: (none)
Log:
A commit
Members:
        v.txt:INITIAL->1.1

Maybe someone with cvsps insight can spot the error? If you don't get the same error I wouldn't be surprised because I had a similar example that would not repeat itself on both of the machines I tried it. This one however "works" every time (on my machines).

-- robin
Next: Linus Torvalds
Message 1 of 4 in “cvsps wierdness”
  1. Robin Rosenberg (list subscriber)Jun 12, 2006
  2. Linus TorvaldsJun 12, 2006
  3. Linus TorvaldsJun 12, 2006
  4. Robin Rosenberg (list subscriber)Jun 13, 2006

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.