Heiko Voigt 9291ccfd27 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>		2009-03-20 23:39:17 -07:00
..
a,v	cvsimport: add test illustrating a bug in cvsps	2009-03-20 23:39:17 -07:00
b,v	cvsimport: add test illustrating a bug in cvsps	2009-03-20 23:39:17 -07:00