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
2009-01-21 22:46:52 -08:00
2009-02-19 23:44:07 -08:00
2008-12-17 21:56:48 -08:00
2009-02-10 21:32:10 -08:00
2008-07-19 11:25:51 -07:00
2008-06-30 22:45:50 -07:00
2008-07-19 11:17:43 -07:00
2009-02-15 01:44:15 -08:00
2008-08-28 20:50:10 -07:00
2008-09-10 15:00:17 -07:00
2008-12-07 15:13:02 -08:00
2009-02-13 23:46:42 -08:00
2008-08-03 14:14:10 -07:00
2008-10-08 08:05:43 -07:00
2009-01-28 11:33:51 -08:00
2008-09-15 23:11:35 -07:00
2009-02-19 23:44:07 -08:00
2008-09-25 09:39:24 -07:00
2009-02-19 23:44:07 -08:00
2009-01-25 17:13:29 -08:00
2009-01-25 17:13:29 -08:00
2009-02-10 21:32:10 -08:00
2009-01-28 11:33:03 -08:00
2009-02-10 21:32:10 -08:00
2009-01-05 13:01:01 -08:00
2008-10-10 08:39:20 -07:00
2008-10-10 08:39:20 -07:00
2009-01-17 18:30:41 -08:00
2009-02-18 11:31:52 -08:00
2008-11-02 16:36:40 -08:00
2009-01-25 17:13:11 -08:00
2009-01-25 17:13:34 -08:00
2009-02-10 21:32:10 -08:00
2009-02-10 22:26:37 -08:00
2008-11-11 14:49:50 -08:00
2008-02-25 23:57:35 -08:00
2009-02-04 13:07:02 -08:00
2009-01-17 18:30:41 -08:00
2008-08-05 21:21:08 -07:00
2008-07-13 14:12:48 -07:00
2009-02-05 19:40:35 -08:00
2008-07-13 14:12:48 -07:00
2009-02-07 00:51:47 -08:00
2008-09-25 08:00:28 -07:00
2009-01-17 18:30:41 -08:00
2008-09-07 23:52:16 -07:00
2009-02-15 01:43:57 -08:00
2008-12-07 15:13:02 -08:00
2008-11-23 19:23:34 -08:00
2009-02-19 23:44:07 -08:00
2008-10-25 12:09:31 -07:00
2009-02-15 01:44:15 -08:00
2008-07-21 19:11:50 -07:00
2009-02-10 22:26:20 -08:00
2009-02-10 22:26:20 -08:00
2009-02-11 18:44:03 -08:00
2009-01-11 13:21:57 -08:00
2009-02-10 22:26:37 -08:00
2008-07-21 19:11:50 -07:00
2009-02-11 02:00:22 -08:00
2009-02-11 18:47:30 -08:00
2008-07-21 19:11:50 -07:00
2008-03-02 15:11:07 -08:00
2009-01-17 18:30:41 -08:00
2008-10-09 11:26:17 -07:00
2009-02-10 22:26:37 -08:00
2009-01-31 17:42:26 -08:00
2008-09-29 07:30:16 -07:00
2009-01-21 23:52:16 -08:00
2009-02-04 16:30:43 -08:00
2009-02-04 16:30:43 -08:00
2009-02-10 22:26:37 -08:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.
See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org. To subscribe
to the list, send an email with just "subscribe git" in the body to
majordomo@vger.kernel.org. The mailing list archives are available at
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%