diff options
| author |  Heiko Voigt <git-list@hvoigt.net> | 2009-03-18 18:33:34 +0100 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2009-03-20 23:39:17 -0700 |
| commit | 9291ccfd27e1e1958b50df7f408996ac22c0776a (patch) | |
| tree | 4be699570e96f8901dec4af05c4d5ea54b83d89f /t/t9603/cvsroot/module/b,v | |
| parent | Add a test of "git cvsimport"'s handling of tags and branches (diff) | |
| download | tgif-9291ccfd27e1e1958b50df7f408996ac22c0776a.tar.xz | |
cvsimport: add test illustrating a bug in cvsps
Some cvs repositories may have time deviations in their recorded commits.
This is a test for one of such cases. These kind of repositories can happen
if the system time of cvs clients is not fully synchronised.
Consider the following sequence of events:
* client A commits file a r1.1
* client A commits file a r1.2, b r1.1
* client B commits file b r1.2 using the same timestamp as a r1.1
This can be resolved but due to cvsps ordering its patchsets solely based
on the timestamp. It only takes revision odering into account if there
is no difference in the timestamp.
I hit this bug when importing from a real repository which was originally
converted from another rcs based scm. Other import tools can handle this
correctly, e.g. parsecvs.
Signed-off-by: Heiko Voigt <hvoigt@hvoigt.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9603/cvsroot/module/b,v')
| -rw-r--r-- | t/t9603/cvsroot/module/b,v | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/t/t9603/cvsroot/module/b,v b/t/t9603/cvsroot/module/b,v new file mode 100644 index 0000000000..ab3089fe56 --- /dev/null +++ b/t/t9603/cvsroot/module/b,v @@ -0,0 +1,40 @@ +head 1.2; +access; +symbols; +locks; strict; +comment @# @; + + +1.2 +date 2009.02.21.18.11.43; author tester; state Exp; +branches; +next 1.1; + +1.1 +date 2009.02.21.18.11.14; author tester; state Exp; +branches; +next ; + + +desc +@@ + + +1.2 +log +@Rev 3 +@ +text +@1.2 +@ + + +1.1 +log +@Rev 2 +@ +text +@d1 1 +a1 1 +1.1 +@ |